Monday, December 19, 2016

%P macros

Syntax errors on the %p macros used inside the 3rd party pixel are preventing the pixels from working as intended.

General %p syntax: %p[start_key_string]![end_character]

The [end_character] should be defined. The end character tells the macro "stop passing values when you hit this character".

Your Floodlight tag looks like follows:

{Insert Floodlight tag that is suffering the issue, with values included if possible}

In the 3rd party pixel, our %p macros are expecting an ending character that will tell them when stop reading, however, this is not implemented at the moment. As a result, when our macro starts reading the value that is coming after the parameter {name of the parameter}, for example, it just keeps reading till the end of the line.

This erros is preventing the pixels from tracking properly. To fix this, add an end character for each %p macros. The [end_character] is typically a semicolon (;) or a question mark (?) to end the string. For example:

- Quantity: %pqty=!;

- Revenue: %pcost=!;

- Order ID: %pord=!?

For more information on DCM macros, please go through the following links.
https://support.google.com/dcm/table/6096962?hl=en&visit_id=1-636177386777577723-156265568&rd=2


https://support.google.com/dcm/answer/2837696?hl=en

2 comments:

  1. Awesome! It’s genuinely awesome article, I even have got obvious idea concerning from this article.
    Dave Keys video marketingy

    ReplyDelete

What to do when you have click discrepancies

 Verify the discrepancy by pulling a CM Report from report builder. Do the publisher and CM report dates match? Are the reports for the same...