What Is Amnet?

Amnet is a programmatic advertising platform under the Dentsu network that provides data-driven solutions for digital media buying. It specializes in real-time bidding (RTB), audience targeting, and campaign optimization to enhance ad performance across digital channels. Amnet integrates advanced technologies to ensure precise audience segmentation and efficient ad delivery while maintaining transparency in media spend. Its capabilities align with Dentsu's mission of enabling seamless and measurable connections between brands and their target audiences.

Getting Started

From Your MetaRouter Account

To gather the Amnet uid value, you must add an Amnet 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 Amnet sync.
3. Fill out the following fields:
   1. Retry Interval (in days) - Default 1 day. Determines the number of days it will take for MetaRouter to attempt an identity sync if the previous attempts have been unsuccessful.
   2. Cookie Lifetime (in days) - Default 365 days. Days before identity sync refreshes for a new ID.
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: fetchPixel

Sync Ids

ids: uid

FetchPixel

• Endpoint: https://ib.adnxs.com/getuidp?callback=WINDOW_CALLBACK
• HTTP method : GET
• Response format: JSON
• Response example : {“uid“:”5c299f0f-c409-4abc-bd10-4e17b5d12eb3”}

Conclusions

Values added to storage

• *_amnet_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.

{
   "amnet": {
     "uid": String
   }
}

UI build settings

• (Required) Retry Interval (in days)
  • Determines the number of days it will take for MetaRouter to attempt an identity sync if the previous attempt(s) have been unsuccessful.
  • Example: 1
• (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