Growthloop Sync

📘

This integration requires activation of additional services. Contact your MetaRouter representative for assistance.

What is GrowthLoop?

GrowthLoop is a composable audience and personalization platform that builds and activates customer audiences directly on top of a company's data cloud. Its Personalization API returns a user's audience memberships and profile attributes for a given identifier, enabling real-time on-site personalization and downstream targeting.


Product Type: Audience Management

Integration Type: ID Sync


Capabilities

  • Looks up a GrowthLoop profile using the configured Lookup Value Source — Anonymous ID (default), User ID, or Hashed Email — and retrieves the user's audience data.
  • Stores the resolved audience data in first-party storage for on-site personalization or downstream targeting.
  • Supports encrypted mode (default; an opaque blob decrypted by the ingestor at event ingest) and unencrypted mode (a trimmed JSON object on-site tools can read from first-party storage).
  • Appends the resolved data to server-side event payloads for audience targeting.

Considerations

  • Important Activation Details: This integration requires activation of additional MetaRouter services to enable the enrichment service. Once activated, the audience data can be securely retrieved and used for on-site personalization and downstream targeting. For assistance activating these services, please contact your MetaRouter representative.
  • The Encrypted setting is on by default, so GrowthLoop's response is stored as a scrambled value only MetaRouter can read — no personal data is readable in the browser. Turn Encrypted off only when an on-site tool needs to read audiences directly from browser storage; because the response can contain personal data, coordinate with MetaRouter before disabling so the exposed fields are filtered. The Fields to Store setting then limits which fields are saved in the browser.
  • When GrowthLoop has no audience match for a user, the sync records a short-lived failure marker (about a day) instead of storing an empty result, then retries after it expires.
  • If the chosen Lookup Value isn't available yet (for example, User ID before the visitor has logged in), the sync records that failure marker and automatically retries once the value becomes available.

Sync Details

  • IDs:

    • data – The GrowthLoop profile object retrieved from the Personalization API for the resolved lookup identifier. Contains the user's audience memberships (and, in encrypted mode, any profile attributes the customer exposes through their Users Dataset or Users Model).
  • Description:

    • The sync retrieves data from GrowthLoop's endpoint via MetaRouter's server-side Enrichment Service, using the configured Lookup Value Source (Anonymous ID by default, or User ID / Hashed Email).
    • The resolved value is stored in first-party storage for the duration set by the Cookie Lifetime setting (defaults to 30 days).
    • The value refreshes after the stored value's TTL expires or it is no longer detected.
    • Encrypted mode stores an opaque blob the ingestor decrypts at event ingest; unencrypted mode stores the JSON object trimmed to the Fields to Store paths.
    • The resolved data is added to server-side event payloads for attribution and targeting.
  • Response Example:

    {
      "entity_id": "550689",
      "entity_name": "customers",
      "audience_count": 2,
      "audiences": {
        "42623": { "audience_name": "Demo Audience" }
      },
      "last_updated_at": "2026-09-29T19:02:41Z"
    }
  • Server-side Event Payload:
    Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload:

    Encrypted mode (default):

    {
      "growthLoop": {
        "encrypted": {
          "data": "String"
        }
      }
    }

    Unencrypted mode places the trimmed object directly under data:

    {
      "growthLoop": {
        "data": {
          "audiences": {
            "42623": { "audience_name": "Demo Audience" }
          },
          "audience_count": 2
        }
      }
    }
  • Cookie Name:

    • Cookie: _meta_growthLoop_data, _meta_growthLoop_data_failure
    • IndexedDB: [your storage prefix]_growthLoop_data, [your storage prefix]_growthLoop_data_failure
    • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

This sync requires a GrowthLoop Personalization API key. Obtain the base64-encoded key from your GrowthLoop team (contact GrowthLoop support if you don't have one) and securely store it for the next step.

2. Add a GrowthLoop Sync in MetaRouter

  • Submit Integration Request Ticket

    • Submit a request through our support portal to enable enrichment services and set up your GrowthLoop Personalization API key. MetaRouter will handle the implementation of the key on your behalf. You may attach a file containing your GrowthLoop API key securely during this step.
    • Example ticket description:
      • Ticket Name: Enable GrowthLoop Enrichment and API Key Implementation
      • Ticket Description: Please enable enrichment services for our GrowthLoop integration and implement our provided API key (attached).
  • Add the GrowthLoop Sync

    • To gather the data value, you must add a GrowthLoop sync.
      1. From the Pipelines page, find the pipeline associated with the web property you'd like to add a sync to. Hover over the three dot dropdown and select "Build AJS File."
      2. In the Identity Syncs section, select the GrowthLoop sync.
      3. Fill out the following fields:
        • MetaRouter Ingestor URL (Required) – Base domain for your MetaRouter ingestor. Exclude https:// and anything after .com. Example: mr.example.com
        • Entity Name (Required) – The GrowthLoop entity (your Users Dataset or Users Model) the profile lookup runs against; it becomes the {entity_name} in the Personalization API path. Use the entity name from your GrowthLoop configuration — check with your GrowthLoop admin or solutions architect if you're unsure. Example: customers
        • Lookup Value Source (Required) – Which MetaRouter identifier supplies the lookup value: Anonymous ID, User ID, or Hashed Email. Example: Anonymous ID
        • Source Connection ID (Optional) – Selects which GrowthLoop source connection store to query. Leave empty to use the default store.
        • Encrypted (Optional) – Toggle, on by default. When on, the profile is stored as a scrambled value only MetaRouter can read. Turn it off only when an on-site tool must read audiences from browser storage, and coordinate with MetaRouter first so personal data is filtered.
        • Fields to Store (Optional) – Comma-separated paths persisted from an unencrypted response; dotted paths select nested values. Ignored when Encrypted is on. Example: audiences,audience_count
        • Cookie Lifetime (in days) (Optional) – How long the synced value remains in first-party storage; when expired or no longer detected, the sync re-triggers. Example: 30
        • API Timeout (in milliseconds) (Optional) – Maximum time the Sync Injector waits for a response from the vendor's API. Example: 300
      4. Scroll down and click the Save and Build File button.
      5. Deploy your AJS file to propagate changes to your web property.