On this page

Moloco

Moloco is a machine learning company that provides performance solutions for digital advertising. Their products include the Moloco Commerce Media (MCM) for online retailers and the Moloco Ads (DSP) for mobile advertising. Both products are powered by Moloco's machine-learning engine, which optimizes campaigns and provides personalized recommendations to customers.

This integration lets you stream events and event properties from Amplitude to Moloco Commerce Media (MCM).

Considerations

Keep these things in mind when sending events to Moloco Commerce Media (MCM):

  • You must enable this integration in each Amplitude project you want to use it in.
  • The Amplitude integration is only compatible with Moloco Commerce Media (MCM).
  • Important: 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 within Moloco Commerce Media (MCM) to associated events. If a user with that ID doesn't exist within Moloco Commerce Media (MCM), Amplitude creates one. Make sure that the Amplitude user_id field matches the Moloco Identity ID to avoid user duplication.
  • Amplitude sends all user properties along with the event.

Setup

Prerequisites

To configure an Event Streaming integration from Amplitude to Moloco Commerce Media (MCM), you need the following information from Moloco Commerce Media (MCM):

  • REST API Key: To send data into Moloco Commerce Media (MCM), you need an API Key. Moloco uses this key to authenticate your requests to the API and connect the data with your account. Find this in your Moloco Commerce Media (MCM) account.

Amplitude setup

  1. In Amplitude Data, click Catalog and select the Destinations tab.
  2. In the Event Streaming section, click Moloco.
  3. Enter a sync name using one of the following values. Then click Create Sync. Create a sync for each event type.
  • ADD_TO_CART
  • ADD_TO_WISHLIST
  • HOME
  • ITEM_SEARCH_VIEW
  • LAND
  • PAGE_VIEW
  • PURCHASE
  • SEARCH
  1. Toggle Status from Disabled to Enabled.
  2. Fill in the following fields
    1. REST API Key: This is the API key provided by moloco
    2. Platform ID: Identifier of the platform (for example, Moloco Demo Test)
    3. Event Type Type of the event this destination delivers. See the available options in step 3 above.
    4. Platform Name: Name of the platform. Should be all lower-cased and replace underscore _ and empty spaces with a hyphen -
  3. Toggle the Send events.
  4. In Select and filter events choose which events you want to send. Choose only the events you need in Moloco. Transformed events aren't supported.
  5. Under Map properties to destination, choose your user identifier and map specific Amplitude properties from Amplitude to Moloco.
  6. When satisfied with your configuration, click Save.

Event types

The following chart provides detailed information for each event type.

  • HOME
    • Description: A shopper viewed your website's main or home page.
  • PAGE_VIEW
    • Description: A shopper visited a page other than the product detail pages or the home page of your site.
    • Additional Required Fields:
      • page_id
      • Anything that can identify the page uniquely. Use window.location.pathname if unsure.
  • ITEM_PAGE_VIEW
    • Description: A shopper visited a product detail page.
    • Additional Required Fields: items
  • ADD_TO_CART
    • Description: A shopper added an item to the cart.
    • Additional Required Fields: items
  • ADD_TO_WISHLIST
    • Description: A shopper put an item into the wish list.
    • Additional Required Fields: items
  • SEARCH
    • Description: A shopper searches items with keywords or phrases from your site.
    • Additional Required Fields: search_query
  • PURCHASE
    • Description: A shopper purchased a product.
    • Additional Required Fields: items, revenue
  • LAND
    • Description: A shopper visited your website from an external source (for example, Google Shopping).
    • Additional Required Fields: referrer_page_id

Mapping chart

See the following chart for the mapping section.

  • platform
    • Native Amplitude Property: Platform
    • Description: Required. string The channel type.
    • Example: Android
  • event_id
    • Native Amplitude Property: Event ID
    • Description: Required. int An event's unique identifier.
    • Example: 1234567890
  • user_id
    • Native Amplitude Property: User ID
    • Description: string A user's unique identifier.
    • Example: testUserID
  • os_name
    • Description: string The device’s OS.
    • Example: Android
  • os_version
    • Description: string The version of the device’s OS.
    • Example: 9.1
  • device_type
    • Native Amplitude Property: Device type
    • Description: string The model of the device.
    • Example: Samsung Galaxy Note 4
  • device_persistent_id
    • Native Amplitude Property: Device ID
    • Description: string The UDID of the device used for the event.
    • Example: English
  • custom_id
    • Native Amplitude Property: Session ID
    • Description: string The session identifier.
    • Example: 12345678912345678
  • language
    • Native Amplitude Property: Language
    • Description: string Language setting of the device.
    • Example: English
  • ip_address
    • Native Amplitude Property: IP Address
    • Description: string IP Address of the device.
    • Example: 198.0.0.1
  • library
    • Native Amplitude Property: Library
    • Description: string Library/User Agent of the device.
    • Example: amplitude-android/3.2.1
  • shipping_charge_currency
    • Description: string The shipping charge’s currency in ISO-4217.
    • Example: USD
  • shipping_charge_amount
    • Description: double The shipping charge without currency.
    • Example: 15.5
  • revenue_currency
    • Description: string The revenue’s currency in ISO-4217.
    • Example: USD
  • revenue_amount
    • Description: double The entire revenue of the event without currency
    • Example: 15.5
  • page_id
    • Description: string Page ID should be a uniquely assigned value for each page in the app or website. Provide a string that can identify the context of the event. Any value will be acceptable if it helps identify unique pages.
    • Example:
      • electronics
      • categories/12312
      • Azd911d
      • /classes/foo/lectures
  • referrer_page_id
    • Description: string Like the referrer in HTTP, this value indicates which page the user came to the current page from.
    • Example: https://mycommerce.com/category/furniture
  • search_query
    • Description: string Query string for the search.
    • Example: microwave ovens
  • items
    • Description: obj Items information.

Use cases

  • Real-time user segmentation: By sending streaming data from Amplitude to Moloco, you can create real-time user segments based on various attributes and behaviors. This enables you to target specific user groups with personalized advertisements and optimize campaign performance accordingly.
  • Dynamic ad creative optimization: By integrating Amplitude's streaming data with Moloco's machine learning engine, you can use real-time user insights to optimize ad creative elements. This includes dynamically adjusting ad content, images, offers, and calls to action based on user preferences and behaviors, resulting in more engaging and effective advertisements.
  • Behavioral retargeting: Amplitude captures user behavior data across various touchpoints, providing valuable insights into user engagement and conversion patterns. By streaming this data to Moloco, you can implement behavioral retargeting strategies, where users who have shown specific behaviors or indicated interest in certain products or services are retargeted with relevant ads across different channels and devices.

Was this helpful?