CiviCRM Community Forums (archive)

As far as I can tell, links that use tokens do not ever get rewritten. That's probably a good thing.

An option (workaround?) might be to have
1) a {mailing.track} that generates the whatever params needed for the tracking code
2) modify the routing code to check if the tracking params exist on the url and call the tracking code (without redirecting)

If we were to go all smart, we could as well not to rewrite the urls that point to civicrm when tracking is enabled and directly add the tracking code

and more generally, we might want to use something else than civi to track the clicks (eg google analytics). It has the trick of tacking into account extra params in the url, we might want to move to a similar syntax so those that use google analytics on their civi install can track from both google and civi?

X+

Trying to figure out how to track the url.

For google, what they have is
Campaign Source (utm_source)
   Required. Use utm_source to identify a search engine, newsletter name, or other source.
Example: utm_source=google

Campaign Medium (utm_medium)
   Required. Use utm_medium to identify a medium such as email or cost-per- click.
Example: utm_medium=cpc

Campaign Term (utm_term)
   Used for paid search. Use utm_term to note the keywords for this ad.
Example: utm_term=running+shoes

Campaign Content (utm_content)
   Used for A/B testing and content-targeted ads. Use utm_content to differentiate ads or links that point to the same URL.
Examples: utm_content=logolink or utm_content=textlink

Campaign Name (utm_campaign)
   Used for keyword analysis. Use utm_campaign to identify a specific product promotion or strategic campaign.
Example: utm_campaign=spring_sale

So might go for something like
example.org/civicrm/profile/edit?utm_source=civimail&utm_medium=email&utm_content=1234&utm_campaign=42&cid=1234&gid=2&cs=dfgpin4

so {mailing.track} expends to
utm_source=civimail&utm_medium=email
&utm_content= contact Id & utm_campaign= mailing id


quite a lot of duplication between the params for the profile/event registration/contribution and tracking, but given that each profile/event registration/contribution/webform url is likely to have different get param (eg. cid or contact_id or contactid id or cid1) not sure I can avoid it.