Creating a Audience who have clicked on specific link in a delivery

[Sengsiong]

Hi all,

We are able to target users who has performed a clicked in the delivery under "Audience Target > Delivery > Clicked".

Is there a way to target contacts who have clicked on a specific link in the delivery?

Regards

SS

[ParthaSarathy · Accepted solution]

Hi @Sengsiong ,

Yes it is possible.

In Query, Select the delivery which you want to target by selecting 'Received' or 'clicked'.

Then under Delivery > drag and drop 'tracking log' > now it will be like 'tracking log exist ', now drag URL under tracking log.

Select 'Source' under URL fields, as below

Click confirm.

Now you will filter out whoever clicked on google.com in that particular Delivery

Regards,

ParthaSarathy S

[Sengsiong]

Thanks! This worked

[csoile]

Hello

Is this possible to do at campaign level rather at email level?

So to target all users that have clicked a specific link in any email in a particular campaign?

[Denis_Bozonnet]

Hi @csoile 

To get the Operations associated to a click, from the tracking Log, you would drill down to the Delivery and form the Delivery you would drill down to Campaign.

You have to go to Advanced mode in the Rules Editor and select the arrow on the right of the Delivery field, scroll down to find Campaign and select the arrow on the right of operations to get the Campaign information.... The query will look like below

Hope this helps,

Thanks

Denis

[csoile]

Hi Denis

Thank you for your prompt response, I have done just that. and that seems to work.

To further specify the URL as above should the query be as below?

[Denis_Bozonnet]

HI @csoile 

Yes for the field to use which holds the URL however the query won't be efficient and performance if you have 2 exist clause. Make sure you the Source URL criteria in the same Exist clause that the delivery campaign criteria... 

Also, since I don't know your volume of Profile, using Exist operator could be quite long since it will scam the whole Profile records whose tracking fit the rules. You might want to start your query at the Tracking Log level by changing the Resource entity in the Property of the query by selecting nmsTrackingLogRcp, (search for tracking in the Resource) and select the profile link in the Target field in the same Query Property....

Again it all depends on your volume of Profile

Hope this helps,

Thanks

Denis

[csoile]

Thanks Denis

your first paragraph makes perfect sense

Im a little unsure with regards to your second paragraph but we do not have a large database, so hopefully the above should be okay.

Many thanks 

C

[Denis_Bozonnet]

Hi @csoile 

Sure no worries on the 2nd element, it's workflow optimisation that is useful to know if case performance start to creak in. The steps are:

Go to Property tab of Query and select the element in Resources

Search Tracking Log and Select nms:trakcingLogRcp

In target, Select Profile

Doing suhc configruation will result that you will query directly the tracking log entity (as opposed query Profile) and you will return the Profile assocaited to the tracking log... You would have duplicated profile as part of the result so after such query you set a Deduplication activity. Sometimes doing it this way is faster 

For low volume at Profile levels, your query will be fine,

Thanks

Denis