As per below doc's reference, Mirror Pages can be retrieved using the mirrorPage node:
https://docs.adobe.com/content/help/en/campaign-standard/using/working-with-apis/interacting-with-ma...
{
"PKey": "<PKEY>",
"category": "email",
"date": "2018-05-17 08:44:49.366Z",
"href": "https://mc.adobe.io/<ORGANIZATION>/campaign/profileAndServices/history/<PKEY>/events/<PKEY>",
"label": "Send via email",
"mirrorPage": {
"href": "https://mc.adobe.io/<ORGANIZATION>/campaign/profileAndServices/history/<PKEY>/events/<PKEY>/mirrorPa..."
},
"type": "outbound"
}
However, the moment href is queried, it seems to trigger Opens for the corresponding link.
Is there a way we could retrieve Mirror Page links without tracking pixels being triggered.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Garima,
I actually had a ticket on similar a few weeks back. Unfortunately at this juncture, Mirror page clicks are registered as unique opens in reporting. An enhancement has been opened (Reference: CAMP-45729) to address this in a future release.
That said if you want to block the tracking pixels in the case of testing a mirror page, you can try blocking the image content.
Regards,
Craig
Views
Replies
Total Likes
Hi Garima,
I actually had a ticket on similar a few weeks back. Unfortunately at this juncture, Mirror page clicks are registered as unique opens in reporting. An enhancement has been opened (Reference: CAMP-45729) to address this in a future release.
That said if you want to block the tracking pixels in the case of testing a mirror page, you can try blocking the image content.
Regards,
Craig
Views
Replies
Total Likes
@Craig_Thonis Thanks a lot for your response !
Views
Replies
Total Likes
Views
Likes
Replies