What Is Amobee?

Amobee is a global marketing technology company that provides data-driven solutions for advertisers and agencies. It offers an integrated platform for media planning, buying, and real-time analytics across various channels, including digital, TV, and social media. Amobee's technology leverages data to deliver personalized and effective advertising campaigns, aiming to enhance audience engagement and return on investment. By utilizing advanced machine learning and data analytics, Amobee helps brands understand consumer behavior and optimize their marketing strategies.

Getting Started

1. From Your Amobee Account

• Gather Client ID - Please reach out to your Amobee support team to gather your Client ID.

2. From MetaRouter

To gather the Amobee uid value, you must add an Amobee 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 Amobee sync.
3. Fill out the following fields:
   1. Consent Type
   2. Client ID - Your Amobee account’s unique client ID.
   3. API Timeout (in milliseconds) - Sets a time limit for how long the Sync Injector will wait for an API response from the vendor. The maximum timeout value is 300ms.
      1. 300 default
   4. Cookie Lifetime (in days) - 365 default
   5. Fire on Re-Sync - ON default
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.

Technical Details

Sync Types

syncType: fetchSync

Sync Ids

ids: uid

FetchSync

• Endpoint: https://d.turn.com/r/dd/id/[CLIENT_ID]/dpuid/[ANONYMOUS_ID]/qry/site_visits/fmt/json
• HTTP method : GET
• Response format: JSON
• Response example : {"uid":"8575821199332081695"}

Conclusions

Values added to storage

• *_amobee_uid
  • Time to live: 365 days
  • Notes: N/A

Server-Side Event Payload: providers object enrichments

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.

{
   "amobee": {
     "uid": String
   }
}

UI build settings

• (Required) Client ID

  • Add your account's unique Client ID here
  • Example: "your-client-id"

• (Required) API Timeout (in milliseconds)

  • Sets a time limit for how long the Sync Injector will wait for an API response from the vendor. The maximum timeout value is 300ms.
  • Example: 300

• (Required) Cookie Lifetime (in days)

  • Defines how long the synced identifier will remain in the first-party ID graph. Once this lifetime is reached, or whenever the sync no longer detects the identifier (whichever comes first), another sync will be performed to pull a new value.
  • Example: 365

• (Required) Fire on Re-Sync

  • Re-syncs for an updated identifier when an Identify call is made.
  • Example: on