Audience Configuration

Audience Configuration plays a key role in your Marigold Moments setup. For websites, it specifies which domains should be monitored for incoming signals using the SDK or API keys. It also maps those signals to a specific audience in your marketing environment, ensuring each triggered Moment is linked to the correct user or profile.

For mobile apps, domain setup is not required. However, an Audience Configuration is still necessary, as it contains the API server key used to recognize and process incoming signals from the app.

Note: The target audience of a Moment is the group of profiles that is targeted by the Moment. In Engage+ this corresponds to the recipient table, in Engage this is an Audience List.

You can create multiple Audience Configurations, combining different domains and audiences, allowing you to handle distinct branches or sub-brands of your organization in a custom way. You can also combine signals from a website or mobile touchpoint in a single Audience Configuration. One Audience Configuration can be used by multiple Moments.

Secondly, an Audience Configuration is essential when defining a Moment, as it links that Moment to a specific setup. Again, for websites, this ensures that the Moment is triggered only when signals from the designated domains are received. For mobile touch points, the Moment will only listen to signals sent using the keys defined in the Audience Configuration.

Example:
A large company with multiple sub-brands addresses cart abandonment differently for each sub-brand, tailoring strategies to distinct audiences.
By setting up multiple Audience Configurations, signals from Brand A's domain can be linked to a specific audience, while signals from Brand B's domain are directed to a different audience. This setup allows for more targeted and personalized marketing efforts for each sub-brand.
Additionally in case of website tracking, by linking an Audience Configuration to a Moment, the Moment becomes applicable only to the specified domains and audiences. This enables marketers to trigger distinct customer journeys for each sub-brand, ensuring that each one receives a customized and effective approach.

 

Audience Configuration overview

The overview provides a view on the existing Audience configurations and their status. The following information is provided:

  • Audience name — The name given to this Audience Configuration. Make it explicit as this name will be shown when configuring a Moment.

  • Domains — The domains that are allowed to send signals to the Signal API for this Audience Configuration. Signals coming from other domains are ignored. This is applicable to website signals only, sent through the Web SDK. Signals coming from other touch points, such as mobile apps, do not require the domain to be filled out.

  • SDK API Signal Status — The status can vary from

    • Key disabled (grey) — The SDK key has not been enabled and no signals can be sent.
    • No signals (yellow) — The SDK key is enabled but no signals have been received yet. Or, the last signal dates from at least 30 minutes ago
    • Signals ok (green) — The SDK key is enabled and signals are coming in. Hovering the status labels provides you with the data of the last incoming signal.

  • Server API Signal Status — The status can vary from

    • Key disabled (grey) — The API key has not been enabled and no signals can be sent.
    • No signals (yellow) — The API key is enabled but no signals have been received yet. Or, the last signal dates from at least 30 minutes ago.
    • Signals ok (green) — The API key is enabled and signals are coming in. Hovering the status labels provides you with the data of the last incoming signal.

    Note: Regeneration of keys does not impact the status.

 

From this overview, you can

  • Edit an existing Audience Configuration

  • Delete an Audience Configuration — Delete is not possible for Audience Configurations that are used in Moments with status running or stopped. An error message is displayed informing the user:

    If the Audience Configuration is not used in a Moment or used in a Moment that is in draft or archived, the Audience Configuration can be deleted.
    Audience Configurations that have been deleted cannot be recovered.

 

Create or edit an Audience Configuration

Note: You need to have at least 1 Audience Configuration to be able to create a Moment.

The Audience Configuration is a one-time set up, defining which domains are allowed to send signals to the Marigold Moments application, what security keys should be used, and which audience list is used to store the data coming from these Signals.
Once the Audience configuration is done, the keys can be used in the SDK or API.

Following properties are set for the Audience configuration:

Global Properties:

  • Name* and Description — Provide a clear name and description for this configuration so it is clear what this will be used for. The Name is mandatory.

Domains

  • Domains* — Provide the list of domains or subdomains, on which events will be tracked and listened to
    These domains can be entered manually, or copy/pasted from an existing list of domains. For the latter, the domain names should be space separated (e.g. example.com example.be example.co.za). This can be handy when there are many domains to be added to the configuration.
    This field is mandatory when the Web SDK API key is enabled.
    It is not mandatory when the server API keys are enabled. This is for instance the case when mobile signals are coming in, using the server API authentication. Mobile signals are not linked to a specific domain.

Audience Mapping

  • Organisation* —This field is only required for Engage. When multiple organisations exist in the marketing environment, select the one that will be used for this integration and in which resides the Audience List.
  • Audience Name* — Select the Audience List/Recipients Table that will be used in your marketing campaigns and for which events are tracked. The list/table selected here must be the same as the audience used in your journey and messages.organization

API Keys

  • SDK API Key —The key used in the SDK and Google Tag manager to communicate with the Marigold Moments application.
    Use the Refresh button to generate a new key when needed.
    The key needs to be enabled to be able to used it in the SDK.
    Once the key is enabled, the domain field is mandatory.

  • Server API Key and secret —The key used by the API to communicate with the Marigold Moments application.
    Use the Refresh button to generate a new key when needed.
    The key needs to be enabled to be able to used it in the SDK.