这是indexloc提供的服务,不要输入任何密码
Skip to content

Protected Audience API and Dynamic Creative Optimization #201

@TheTamFamily

Description

@TheTamFamily

Morning,

For context, in the current programmatic retargeting using 3P cookies I am able to run Dynamic Creative Optimization (DCO) campaigns using a combination of Campaign Manager 360 (CM360) Floodlight variable and Google Studio (Product Catalog). The way this works, when a user browse a product on the advertiser's website the product ID is sent to CM360 via Floodlight variable using the user's 3P cookie. This means that I can create a single interest group say "product viewed" and the right product image is shown in the Display ad.

In PAAPI there is the adComponents attribute and the documentation says:

"Null or a list of interest group ad. Contains various ad components (or "products") that can be used to construct ads composed of multiple pieces — a top-level ad template "container" which includes some slots that can be filled in with specific "products"."

In this scenario:

When user A visits Advertiser website he is particularly interested in shoes. I create an interestGroup named shoes with the following ads and adComponents (please ignore the JSON formatting for now):

ads: [ { renderUrl: 'https://www.examle.com/ig1/ad.html', } ] adComponents: [ { renderUrl: 'https://www.example.com/ig1/runningshoes.jpg', metadata: { productId: ‘11111’, }, renderUrl: 'https://www.example.com/ig1/hikingboots.jpg', metadata: { productId: '12345', }, } ]

When user B visits the same Advertiser website she is also interested in shoes and I add her to the same interestGroup.

My question is how would user A see runningshoes.jpg and user B sees hikingboots.jpg. Is this the correct way to view the use of adComponents?

Thanks,

David

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions