Breaking change in generate placement tags

[maranz hiberus]

Hi team,

We have found out an unpleasant surprise with the generate tags functionality (https://developers.google.com/doubleclick-advertisers/v3.4/placements/generatetags)

After the change to Campaign Manager 360, a new option box named "Include TCF GDPR macros" has appeared on the UI of DCM.

When we requested through the API the tags, prior to this change, we obtained the following:

<ins class='dcmads' style='display:inline-block;width:1px;height:1px'

    data-dcm-placement='N5074.3658049HPHES/B24925044.286236006'

    data-dcm-rendering-mode='iframe'

    data-dcm-https-only

    data-dcm-gdpr-applies='gdpr=${GDPR}'

    data-dcm-gdpr-consent='gdpr_consent=${GDPR_CONSENT_755}'

    data-dcm-addtl-consent='addtl_consent=${ADDTL_CONSENT}'

    data-dcm-resettable-device-id=''

    data-dcm-app-id=''>

  <script src='https://www.googletagservices.com/dcm/dcmads.js'></script>

</ins>

But right now, the same call is obtaining, for the same placement, the following:

<ins class='dcmads' style='display:inline-block;width:1px;height:1px'

    data-dcm-placement='N5074.3658049HPHES/B24925044.286236006'

    data-dcm-rendering-mode='iframe'

    data-dcm-https-only

    data-dcm-resettable-device-id=''

    data-dcm-app-id=''>

  <script src='https://www.googletagservices.com/dcm/dcmads.js'></script>

</ins>

As you can see, GDPR macro is not present currently when downloading tags through the API (though it is a default option in the UI). This is a breaking change for which we were unaware that is causing us impact on production. Could you take a look at it and get back to us as soon as possible?

Regards,

Miguel Angel

[maranz hiberus]

Hello again,

I have verified that not only INS tags are affected; all of those that should have had GDPR macro are impacted. It just doesn't add this macro to any of them by default.

Please advise, this is a urgent matter for us - our users have had to fall back to export manually the tags from the UI which increases the workload.

Regards,

Miguel Angel

[maranz hiberus]

Hi team,

Is there any update on this issue? We would need to know what is going to be done (if you are going to recover previous behavior, API is going to be modified to allow requesting GDPR/ no GDPR macros, or if you pretend to keep the current behavior) and an estimated time of resolution.

Keep in mind that any additional development that could be needed on our side to adapt is going to add time on top of your resolution, so knowing what and when to expect it would help us greatly to advance any needed changes on our side, and also inform an estimated time for our users in which our custom downloading of tags will be available for use again.

Regards,

Miguel Angel

--
You received this message because you are subscribed to the Google Groups "Google's DoubleClick Campaign Manager API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-doubleclick-for-ad...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-doubleclick-for-advertisers-api/cb8b9ea3-73da-4819-bd8c-98557793aad2n%40googlegroups.com.

[DCM API (DoubleClick Campaign Mgr)]

Hi Maranz,

Thank you for raising this to us. Could you please provide the following details via Reply privately to author option?

• DCM account ID
• Profile ID
• request body and API response in JSON format

Also, is the behavior occurs recently (after After the change to Campaign Manager 360)? Could you confirm if the GDPR macro is present when downloading tags through the API before?

Regards,

Teejay Wennie Pimentel DCM API Team

ref:_00D1U1174p._5004Q27szPV:ref

[Avihay Avitan]

Hi Teejay, 

We experience the same issue, so it would be hard to believe it is related to specific account id or profile id.

Confirming the GDPR macro is present when downloading tags through the API before. 

This affects production operation right now, please provide an update ASAP.  

Thank you!

[DCM API (DoubleClick Campaign Mgr)]

Hi Avihay,

Thank you for reporting this. Please be informed that the team is currently on the testing and evaluation phase for the aforementioned fix. I'll update this thread as soon as the fix has been released.

[Alba Cuevas]

Hi,

Any updates on this? We are also tracking this chain for a solution, anything that can be shared is appreciated.

Thanks!

[maranz hiberus]

Hi team,

We have seen that today GDPR macros are being downloaded again by defult.

With all due respect, please, next time it would be nice to know in advance from you before rolling out the change to production; on our application code we added a temporary patch to manually insert GDPR macros (fortunately, we had the foresight to take in account checking first if they were already present to avoid messing it up). Or at least to know that you have deployed it and not to have to be informed by our users whenever they notice.

Going on to the issue at hand now:

• Prior to change to Campaign 360, API was always downloading tags with GDPR macros.
• After change to Campaign 360, API was missing  GDPR macros silently.
• Right now, the behavior has set up again to always download tags with GDPR macros, which was the original behavior. Thus, it seems to be solved.

I would like to ask if you are planning to add to the API call the same option functionality to allow choosing either to have GDPR macro or not, as these few days, our users have been taking advantage of being able to choose so in our app (we let them to download the tags without changes or forcing GDPR macros through our code patch).

If there is a roadmap to add this option, I would like very much to know an estimated time to deploy it in production. If there is no plan to add it, please pass along a feature request and let us know if/when would you be able to take care of it. Mostly, we want to know if we should start developing a temporary patch from our side to be able to remove GDPR macros should this option take too long to be available (as it impacts non-EU campaigns).

As a note, I suppose it would be a good idea to have in mind other options that the UI provides that are not available on the generatePlacements method in future changes (include dc_dbm macro, for example). We have still no real need for this one, but being able to choose the same options with which you would generate a tag in the UI would make sense.

Regards,

Miguel Angel

[DCM API (DoubleClick Campaign Mgr)]

Hi Miguel,

Thank you for sharing your feedback and inquiries. Let me relay this to the rest of the team to get their insight. I'll update this thread the soonest they provide their feedback.

[DCM API (DoubleClick Campaign Mgr)]

Hi Miguel,

 

I'm Michael from DCM API Team.

 

I just want to circle back on this and let you know that the issue here has been fixed. Let us know should you have any more concern.

 

Regards,

Michael Angelo Legaspi DCM API Team

ref:_00D1U1174p._5004Q27szPV:ref