Moloco Commerce Media (MCM) is a commerce media platform that leverages retailer's first-party data and machine learning to deliver highly relevant ads, optimizing ad performance and personalizing user experiences. It offers real-time bidding, ad delivery, and performance insights for retailers and advertisers.
MetaRouter facilitates server-side event collection through Moloco's Events API, enabling secure and reliable data transmission to Moloco's infrastructure. Customers can use this integration to capture critical shopper behavior and event data for campaign optimization and personalization.
Product Type: Advertising
Integration Type: Starter Kit
Event Source Type: Web, Mobile Browser, and Mobile App
Event Scope: Full-Funnel Events
- Event API Support: MetaRouter sends shopper behavioral events (e.g., page views, product views, add-to-cart, and purchases) to Moloco's Events API.
- Identity Handling:
- MetaRouter uses the
anonymousId as the device.persistent_id for consistent user identification.
- Device information, such as OS, OS version, user agent, and model, is included in the payload.
- Support for Event-Specific Parameters: Payloads include key attributes such as product details, revenue, and quantities, as defined in Moloco's Events API Reference.
- Session Started Event: This event is triggered by the MetaRouter sync when a new session begins. To enable this event, you must integrate the MetaRouter sync. Contact your MetaRouter support team for more details.
- Endpoint: The endpoint URL to send event data is provided directly by your Moloco representative. Contact your Moloco representative for your endpoint.
- API Key: Required to authenticate requests to Moloco's Events API. Follow Moloco's documentation to manage or generate API credentials.
- From the integration library, add a Moloco Commerce Media integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|
ENDPOINT | The Moloco endpoint URL provided by your Moloco representative. Include the full endpoint URL here. |
API_KEY | The API key used to authenticate requests to Moloco's Events API. |
- MetaRouter provides all of the event mappings that Moloco Commerce Media integrations typically require. You may add custom events, parameters, or mappings in accordance with Moloco's API documentation.
- In the Pipelines tab, add your Moloco Commerce Media integration.
- Select the correct integration revision.
- Click Add Integration to finalize deployment.
Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.
| Output Key | Description | Expected Input |
|---|
id Required | String: A unique identifier for the event. | messageId |
user_id Required | String: The unique identifier of the user performing the event. | userId |
timestamp Required | Integer: The event timestamp in milliseconds since the Unix epoch. | Expression – converts the event timestamp to milliseconds since epoch |
device.persistent_id Required | String: The persistent device ID used to track users. | anonymousId |
channel_type Required | String: Indicates the event source. APP for app events and SITE for web events. | Expression – returns APP when app/device/OS context exists, otherwise SITE |
device.os Recommended | String: The operating system of the device. | Expression – returns ios or android from context.device.type |
device.os_version Recommended | String: The version of the operating system. | context.os.version |
device.model Recommended | String: The device model name. | context.device.model |
device.ua Recommended | String: The user agent of the device. | context.userAgent |
language | String: The user's preferred language. | Expression – extracts the language from context.locale (e.g., en) |
page_id Recommended | String: The ID or path of the current page. | context.page.path |
referrer_page_id Recommended | String: The ID or URL of the referrer page. | context.page.referrer |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., PAGE_VIEW, HOME). | Expression – returns HOME when page path is /, otherwise PAGE_VIEW |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., PAGE_VIEW, HOME). | Expression – returns HOME when the screen name is home, otherwise PAGE_VIEW |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., SEARCH). | Enrichment – 'SEARCH' |
search_query Required | String: The search term used by the user. | properties.query |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., ITEM_PAGE_VIEW). | Enrichment – 'ITEM_PAGE_VIEW' |
items Required | Array: Builds the viewed product item with id, price (currency and amount), and quantity. | Expression – builds the item from properties |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., ADD_TO_CART). | Enrichment – 'ADD_TO_CART' |
items Required | Array: Builds the added product item with id, price (currency and amount), and quantity. | Expression – builds the item from properties |
revenue | Object: Builds revenue with currency and amount (price × quantity). | Expression – builds revenue from properties |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., ADD_TO_WISHLIST). | Enrichment – 'ADD_TO_WISHLIST' |
items Required | Array: Builds the wishlist product item with id, price (currency and amount), and quantity. | Expression – builds the item from properties |
revenue | Object: Builds revenue with currency and amount (price × quantity). | Expression – builds revenue from properties |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., LAND). | Enrichment – 'LAND' |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., LAND). | Enrichment – 'LAND' |
| Output Key | Description | Expected Input |
|---|
event_type Required | String: Describes the event type (e.g., PURCHASE). | Enrichment – 'PURCHASE' |
items Required | Array: Builds a list of purchased product items, each with id, price (currency and amount), and quantity. | Expression – builds items from properties.products |
revenue Required | Object: Builds revenue with currency and the summed amount across products. | Expression – builds revenue from properties.products |
shipping_charge | Object: Builds the shipping charge with currency (default USD) and the shipping amount. | Expression – builds shipping charge from properties.shipping |
These identifiers must be mapped to Moloco Commerce Media in order for successful user matching to occur. Without these IDs, any events sent to Moloco Commerce Media may not be accurately reflected in reporting. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.
| Attribute | Example | Sync Injector Required? |
|---|
user_id Required | 123456 | No |
device.persistent_id Required | abc123-anonymous-id | No |
Coordinate with your Moloco representative, or use the Moloco Commerce Media dashboard, to confirm that events are being received and processed correctly on their backend.
