Moloco

Use GrowthLoop audiences for Moloco targeting over Google Cloud Pub/Sub.

Connect this destination to export audience membership as enter and exit events on a Pub/Sub topic, for use in Moloco targeting.

This destination writes to your Moloco account and is a good fit when you want to:

  • Make audience enter and exit events available in Moloco
  • Match contacts on user ID

This maps to GrowthLoop Audiences and Journeys:

Use it forAudiencesJourneys
Publishing audience enter and exit events to Moloco✓✓

Prerequisites

Make sure you have:

  • A Moloco account and a Moloco representative for this integration.
  • A Google Cloud Pub/Sub topic dedicated to this platform. Use the topic name, such as moloco-audiences, or the full path, such as projects/my-project/topics/moloco-audiences.
  • A Google Cloud service account JSON key with permission to publish to that topic. Create the service account in your project and share it with Moloco, or ask Moloco to create the account and send you the key.

Set up Moloco as a destination

  1. In GrowthLoop, click the Destinations tab on the left sidebar.
  2. Click New Destination in the top right corner.
  3. Search for Moloco and click Add Moloco.
  4. Enter the required information, then click Create.
FieldDescription
Destination NameName this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Moloco Ads".
Sync FrequencySet the default export frequency (for example, daily or weekly). You can override this setting for individual exports.
TopicPub/Sub topic name or full projects/{project}/topics/{topic} path from Moloco.
CredentialsThe full service account JSON key.

GrowthLoop validates that it can publish with that key. Moloco then appears in your list of connected destinations.

Export to Moloco

From within GrowthLoop, export from an audience or from a journey Destination Node. See Export an audience or Build a journey if you need more information on these steps.

After building or selecting an audience, click Export, then search for Moloco. In a journey, add a Destination Node under Ads and select Moloco.

Journey Destination Node with export name, match fields, and personalization signals

Map identifiers

On an audience or in a journey Destination Node, map User ID. This field is required.

You can also map Persistent ID for a device identifier such as IDFA or GAID.

Match fieldRequiredDescription
User IDYesYour user identifier
Persistent IDNoDevice identifier such as IDFA or GAID

Configure the export

This is where you set the campaign type and schedule for audience exports. On a journey Destination Node, you set timing on the journey canvas.

SettingAudience exportJourney Destination Node
Export NameDefaults to {audience name}_GL_Audience_{audience ID}.Required. Enter a name so you can find the export in GrowthLoop.
Campaign typeChoose a one-time or ongoing export.The journey schedule controls when the journey runs and contacts are sent to Moloco.
ScheduleSet frequency, start date, end date, and days of the week for ongoing exports.Users reach this node when the journey runs. Add a Delay Node or set Criteria Evaluation to control timing.

Export behavior

This is what GrowthLoop writes when you export an audience.

BehaviorWhat happens
What GrowthLoop writesJSON events on the Pub/Sub topic. Direction is GrowthLoop → Moloco.
When it runsGrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. Journeys send exports on demand when users reach the Destination Node.
Audience IDGrowthLoop sends aud_{audience ID}_{slugified audience name}.
Match fieldsUser ID is required. Persistent ID is optional.
AddsGrowthLoop publishes a members_enter_audience event with the mapped IDs.
RemovesGrowthLoop publishes a members_exit_audience event with the mapped IDs.
One-time exportsGrowthLoop sends current membership once as enter events.
Ongoing adds and removalsOngoing exports publish enter events for contacts who join and exit events for contacts who leave.
DeletesGrowthLoop does not delete Moloco objects beyond those exit events.

Confirm the export was successful

When the run finishes, confirm you can use the data in Moloco.

  • Audience export: Open your Moloco dashboard and look up the audience. You can also check the Pub/Sub topic in Google Cloud.
  • Journey Destination Node: Open your Moloco dashboard and look up the audience named after the export.

In GrowthLoop, review counts on the audience Exports tab, or open the Activity tab on the journey Destination Node. See Export an audience or Monitor a journey for more information.

Congrats on successfully exporting to Moloco!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

ProblemCauseResolution
Connection fails to validateThe JSON key is incomplete, or the service account cannot publish to the topicPaste the full JSON key. Confirm the account can publish to the Topic you entered
Rows fail to exportUser ID is not mappedMap User ID
Moloco does not show the audienceEvents landed in a different topic, or Moloco has not ingested themConfirm Topic matches the topic Moloco prepared, then check the Moloco dashboard again

What’s Next

Export an audience after you connect a destination

Did this page help you?