Leiste mit Community-Erfolgen erweitern.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.

GELÖST

Parse query string parameters in eVars using processing rules

Avatar

Ehemaliges Community-Mitglied

I have a client that is running an out dated s code version with a channel manager plugin that is not supported. While the plugin does still capture the campaign id, it doesn't parse the contents of it into the correct evars.

What I am wondering is if we add additional parameters to the query string as below, can we use processing rules to parse those values into an evar?

As an example the query string might be:

?cmpid=test&cmreferrer=Google&cmsource=Paid&cmmedium=PPC&cmcontent=Branded

What we'd like to happen is to have:

cmpid=test stored as campaign first/last
cmreferrer stored in evar 48
cmsource stored in evar 49
cmmedium stored in evar 50
cmcontent stored in evar 51.

Is accomplishing this with only processing rules possible, or do we need to use java script to parse them?

Thanks!

1 Akzeptierte Lösung

Avatar

Korrekte Antwort von
Employee

Yes processing rules can handle parsing a query string and setting the defined value into a given Custom Conversion (eVar) variable- example below:

https://marketing.adobe.com/resources/help/en_US/reference/processing_rules_populate_campaign_ID.htm...

https://marketing.adobe.com/resources/help/en_US/reference/processing_rules_about.html

Best,

Brian

Lösung in ursprünglichem Beitrag anzeigen

1 Antwort

Avatar

Korrekte Antwort von
Employee

Yes processing rules can handle parsing a query string and setting the defined value into a given Custom Conversion (eVar) variable- example below:

https://marketing.adobe.com/resources/help/en_US/reference/processing_rules_populate_campaign_ID.htm...

https://marketing.adobe.com/resources/help/en_US/reference/processing_rules_about.html

Best,

Brian