Moloco
Moloco is a machine learning company that provides performance solutions for digital advertising. Moloco products include Moloco Commerce Media (MCM) for online retailers and Moloco Ads (DSP) for mobile advertising. Both products are powered by Moloco's machine-learning engine, which optimizes campaigns and provides personalized recommendations.
This integration streams events and event properties from Amplitude to Moloco Commerce Media (MCM).
Use cases
- Real-time user segmentation: Stream data from Amplitude to Moloco to create real-time user segments based on attributes and behaviors. Target specific user groups with personalized ads and optimize campaign performance.
- Dynamic ad creative optimization: Use real-time user insights from Amplitude with Moloco's machine learning engine to optimize ad creative. Dynamically adjust ad content, images, offers, and calls to action based on user preferences and behaviors.
- Behavioral retargeting: Stream Amplitude user behavior data to Moloco to retarget users who showed specific behaviors or interest in certain products across channels and devices.
Considerations
Keep these points in mind when sending events to Moloco Commerce Media (MCM):
- Enable this integration in each Amplitude project that needs it.
- The Amplitude integration is only compatible with Moloco Commerce Media (MCM).
- You need a Moloco Commerce Media (MCM) account to enable this integration. If you don't have one, contact Moloco.
- Amplitude matches the user ID to the ID field in Moloco Commerce Media (MCM) to associate events. If a user with that ID doesn't exist in Moloco Commerce Media (MCM), Amplitude creates one. The Amplitude
user_idfield must match the Moloco Identity ID to avoid user duplication. - Amplitude sends all user properties along with the event.
Set up the integration
Prerequisites
To configure an Event Streaming integration from Amplitude to Moloco Commerce Media (MCM), you need the following from Moloco Commerce Media (MCM):
- REST API Key: Moloco uses this key to authenticate your requests and connect data with your account. Find this key in your Moloco Commerce Media (MCM) account.
Amplitude setup
- In Amplitude Data, click Catalog and select the Destinations tab.
- In the Event Streaming section, click Moloco.
- Enter a sync name using one of the following values, then click Create Sync. Create a sync for each event type.
ADD_TO_CARTADD_TO_WISHLISTHOMEITEM_SEARCH_VIEWLANDPAGE_VIEWPURCHASESEARCH
- Toggle Status from Disabled to Enabled.
- Fill in the following fields:
- REST API Key: The API key provided by Moloco.
- Platform ID: Identifier of the platform (for example,
Moloco Demo Test). - Event Type: Type of event this destination delivers. Refer to the available options in step 3 above.
- Platform Name: Name of the platform. Use all lowercase and replace underscore
_and empty spaces with a hyphen-.
- Toggle the Send events.
- In Select and filter events, choose which events to send. Choose only the events you need in Moloco. Transformed events aren't supported.
- Under Map properties to destination, choose your user identifier and map specific Amplitude properties to Moloco.
- Click Save.
Event types
The following table provides details for each event type.
| Event type | Description | Additional required fields |
|---|---|---|
HOME | A shopper viewed your website's main or home page. | None |
PAGE_VIEW | A shopper visited a page other than a product detail page or the home page. | page_id (anything that identifies the page uniquely; use window.location.pathname if unsure) |
ITEM_PAGE_VIEW | A shopper visited a product detail page. | items |
ADD_TO_CART | A shopper added an item to the cart. | items |
ADD_TO_WISHLIST | A shopper added an item to the wish list. | items |
SEARCH | A shopper searched items with keywords or phrases. | search_query |
PURCHASE | A shopper purchased a product. | items, revenue |
LAND | A shopper visited your website from an external source (for example, Google Shopping). | referrer_page_id |
Mapping chart
The following table lists the fields available for mapping.
| Field | Native Amplitude property | Type | Description | Example |
|---|---|---|---|---|
platform | Platform | string | Required. The channel type. | Android |
event_id | Event ID | int | Required. An event's unique identifier. | 1234567890 |
user_id | User ID | string | A user's unique identifier. | testUserID |
os_name | string | The device's OS. | Android | |
os_version | string | The version of the device's OS. | 9.1 | |
device_type | Device type | string | The model of the device. | Samsung Galaxy Note 4 |
device_persistent_id | Device ID | string | The UDID of the device used for the event. | |
custom_id | Session ID | string | The session identifier. | 12345678912345678 |
language | Language | string | Language setting of the device. | English |
ip_address | IP Address | string | IP Address of the device. | 198.0.0.1 |
library | Library | string | Library or User Agent of the device. | amplitude-android/3.2.1 |
shipping_charge_currency | string | The shipping charge's currency in ISO-4217. | USD | |
shipping_charge_amount | double | The shipping charge without currency. | 15.5 | |
revenue_currency | string | The revenue's currency in ISO-4217. | USD | |
revenue_amount | double | The entire revenue of the event without currency. | 15.5 | |
page_id | string | A uniquely assigned value for each page in the app or website. Provide a string that identifies the context of the event. | electronics, categories/12312, Azd911d, /classes/foo/lectures | |
referrer_page_id | string | Like the referrer in HTTP, this value indicates which page the user came from. | https://mycommerce.com/category/furniture | |
search_query | string | Query string for the search. | microwave ovens | |
items | obj | Items information. |
Was this helpful?