Solved! Go to Solution.
OK. If you can’t use Velocity to generate links, I think using {{campaign.id}} is your only path forward.
We have instances where a smart campaign is sending more than one email for example if a drip-style send is requested.
If you switch those to executables, you’ll have a unique {{campaign.id}}. Shouldn’t be too tough.
We also have instances where an email program (not a smart campaign) is sending a program.
There’s an underlying {{campaign.id}} for those, so that’s fine.
Another method is to use Munchkin to send a synthetic Click Link activity (that is, in addition to the automatic Click Email) that includes the Email ID. You will need a developer for this.
To improve our tracking and data collection in Adobe Analytics, we would like to have a unique identifier, like the Email Asset ID, as a parameter on all the URLs in our emails. This will ensure that the identifier is associated with each individual email, making it readily available and captured for tracking purposes in Adobe Analytics.
We have instances where a smart campaign is sending more than one email for example if a drip-style send is requested. We also have instances where an email program (not a smart campaign) is sending a program.
OK. If you can’t use Velocity to generate links, I think using {{campaign.id}} is your only path forward.
We have instances where a smart campaign is sending more than one email for example if a drip-style send is requested.
If you switch those to executables, you’ll have a unique {{campaign.id}}. Shouldn’t be too tough.
We also have instances where an email program (not a smart campaign) is sending a program.
There’s an underlying {{campaign.id}} for those, so that’s fine.
Another method is to use Munchkin to send a synthetic Click Link activity (that is, in addition to the automatic Click Email) that includes the Email ID. You will need a developer for this.
The only supported way to use tracked links + Velocity is to output the entire <a>
tag from Velocity.
But let’s step back and make sure we don’t have an XY Problem. What is the full business requirement (not specific technical implementation) that you are trying to meet?