Add to SFDC campaign flow from "Clicked Link on Webpage"

[Anonymous]

Hi,

I am trying to track the number of downloads we have on our website and will be using the SFDC campaigns to track this. However, I am having troubles with the flow working correctly.

All of our download links have the same URL but the querystring contains the file ID number associated to the document downloaded. The smartlist works great and is able to track the action. However, the flow step is not working correctly. When I try to break it out by the file ID number, the action is skipped.

Smartlist:

Flow:

What I see in results:

Help? What I am doing wrong? If I do not group several documents in one, then I will have to create nearly 400 smart campaigns to track these downloads! eeek. I don't think my fingers or patience could handle that.

[John_Clark1]

Hi Brooke,

I've been doing some testing in my stage instance, but I'm not coming up with a way to make this work.  The trouble is that the choice in the flow step which looks at Clicked Link On Web Page is only looking at the url, and the query string doesn't count as part of that.

Any way I try to work with the problem, it looks like it would require one campaign per query string value.  Is there anywhere else that value gets listed?  Any other field you might be able to base the choices on?

John

[Anonymous]

Thanks for your response John! Unfortunately, there is not another field I could pull from. I’m going to talk to the website programmer to see if there is anything on his end that he could do with how the URLs are generated. Hopefully I can figure something out.

[John_Clark1]

I'd be interested in hearing any solution you come up with.  I would also encourage you to post this as an idea.  If it was possible to base the choice off the query string that was appended to the url which triggered the campaign, then your original set up would work as expected.  This may be something that our product managers could implement if there was enough push for it.

John

[SanfordWhiteman]

Add the file ID to the document #hash.  This is considered part of the URL for Flow purposes.

[Anonymous]

I'm not following. Can you elaborate?

[SanfordWhiteman]

In addition to adding ?fid=2583, append #2583 to the URL.

The document hash is considered part of the Clicked Web Page event. This is different from the querystring, which is stored separately and can't be used as a constraint in all contexts.