Moloco Commerce Media

Send conversion events to Moloco for commerce media campaign attribution, machine learning-based optimisation, and retail media performance measurement.

Prerequisites

Complete these steps in the Moloco platform before configuring the integration in Signal.

Create or access your Moloco account

Log in to Moloco Commerce Media dashboard. If you don’t have an account, contact Moloco sales to set up a commerce media account. You’ll need platform-level access to retrieve credentials and configure event tracking.

Get your Platform ID from the Moloco dashboard

Navigate to Platform Settings in the Moloco Commerce Media dashboard. Your Platform ID is the unique identifier for your commerce media platform and is displayed prominently in the settings overview.

Create an API key and Event Token from Settings

Navigate to Settings > API Keys in the Moloco dashboard. Click Create Key to generate a new API key for server-side event delivery.
Navigate to Events > Configuration and locate your Event Token. This token is used for conversion attribution and is separate from the API key.
Store both credentials securely — they may only be shown once at creation time.

Configuration

Field	Type	Required	Description
`platform_id`	string	Yes	Your Moloco platform ID. Found in the Moloco Commerce Media dashboard under Platform Settings.
`api_key`	secret	Yes	API key for authenticating server-side event delivery. Generate in the Moloco dashboard under Settings > API Keys.
`event_token`	secret	Yes	Event tracking token for conversion attribution. Found in the Moloco dashboard under Events > Configuration.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Moloco Commerce Media or filter by Advertising.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/moloco/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Moloco Commerce Media",
    "variant": "default",
    "config": {
      "platform_id": "plat-moloco-12345",
      "api_key": "ak_moloco_abc123...",
      "event_token": "et_moloco_xyz789..."
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal Event	Moloco Event	Description
`purchase`	`PURCHASE`	Completed transaction with revenue and item details
`add_to_cart`	`ADD_TO_CART`	Product added to shopping cart
`page_view`	`PAGE_VIEW`	Standard page view tracking
`product_view`	`ITEM_PAGE_VIEW`	Product detail page view
`search`	`SEARCH`	Search query performed
Custom events	Custom conversion	Map any Signal event to a custom Moloco event type via blueprint configuration

Event mappings are fully configurable through blueprints. The table above shows common default mappings — you can customise these to match your commerce media attribution goals.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Moloco API. No client-side scripts are loaded for this integration.

Testing

Install the integration with your Platform ID, API key, and Event Token.
Trigger a test event (e.g. a purchase or product view) on your site with the Datafly.js collector active.
Check the Live Events view in Signal to confirm the event was captured.
Verify the event appears in the Moloco Commerce Media dashboard under event reporting.
Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

⚠️

Moloco’s ML-based attribution may take several hours to fully process conversion events and reflect them in campaign performance reports.

Troubleshooting

Issue	Resolution
`401 Unauthorized`	Verify your API key is correct and has not been revoked. Regenerate in Moloco Settings > API Keys if needed.
`403 Forbidden`	Check that the Event Token is valid and matches the Platform ID. Regenerate the token in Events > Configuration if needed.
`404 Not Found`	Check that the Platform ID matches your account exactly.
Events not appearing in Moloco	Confirm the integration is enabled in Signal and check the Delivery Log for errors. Moloco may take several hours to fully process conversions.
`400 Bad Request`	Verify event payload includes required fields (e.g. item details for purchase events). Check blueprint mappings.
`429 Too Many Requests`	Moloco rate limits are being hit. Signal will automatically retry with backoff.

Visit Moloco Commerce Media documentation for full API documentation and credential setup instructions.

MiQ (Xandr)Nextdoor