Detect tracking URLs
- Topics:
- Monitoring
CREATED FOR:
- User
- Developer
Example of non-detection
<%= getURL("http://mynewsletter.com") %>
works and sends the actual content of the web page via email to the recipients. But none of the links are tracked. The reason for this is that the MTA executes "<%=getURL(..."
for each email before sending. It can be different for each recipient, so Adobe Campaign cannot know the URLs for tracking and assign them a tag ID.
When the page to download is the same for all recipients, the best practice is to do the following:
<%@ include url="http://mynewsletter.com" %>
In that case, the page is downloaded during the analysis, before the tracking detection. It allows Adobe Campaign to discover the links, assign a tag ID, and track them.
Recommended Pattern
After processing <%@
instructions, the URL to be tracked has the following syntax: <a href="http://myurl.com/a.php?param1=aaa¶m2=<%=escapeUrl(recipient.xxx)%>¶m3=<%=escapeUrl(recipient.xxx)%>">
Unsecured pattern
When adding personalized links to your content, always avoid having any personalization in the hostname part of the URL to avoid potential security gaps. Learn more in this page.
For example, the <a href="http://<%=myURL%>">
syntax is not secure and must be avoided.
- Using this syntax can lead to security issues if the link generated by Adobe Campaign contains one or more parameters.
- Tidy can incorrectly patch some of the links, which can happen randomly. The typical symptom is a piece of HTML that is visible in the email proofs but not in the preview.
- Escaping of the URL is problematic, some characters in the URL can cause problems.
- You cannot have a parameter named ID conflicting with parameter in the redirection URL.
- Interest of tracking is then limited to statistics on the delivery, as Adobe Campaign indifferently tracks all possible values of “myURL”.
Campaign
- Campaign v7 documentation
- Release notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- CRM connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Configure external accounts
- Configure Federated Data Access
- Get started with Federated Data Access
- Best practices and limitations
- Configuration guidelines
- Configuration steps
- Configure Amazon Redshift
- Configure Azure Synapse
- Configure Google BigQuery
- Configure Hadoop
- Configure Microsoft SQL Server
- Configure Netezza
- Configure Oracle
- Configure PostgreSQL
- Configure SAP HANA
- Configure Snowflake
- Configure Sybase IQ
- Configure Teradata
- Configure Vertica Analytics
- Remote access rights
- Connect to the database
- Create the data schema
- Define data mapping
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel