Show experience only once | Adobe Higher Education
Skip to main content
Level 2
June 10, 2021
解決済み

Show experience only once

  • June 10, 2021
  • 3 の返信
  • 3675 ビュー

Hi, when creating an experience targeting activity (using VEC), how do I set it to such a way that I want to suppress a qualified visitor who has already seen the experience from not seeing it again? I want them to see the experience ONLY once, in let's say for example, once in a calendar month.

I believe profile script could be one option, but that would be a challenge, given that VEC uses "global-target-mbox"? Any other solution?

このトピックへの返信は締め切られました。
ベストアンサー ryanr7

Hi @jaredho

It depends a little. If you are using Target as your reporting source and your goal metric is set to viewed an mbox > ** display mboxes ** then changing the advanced settings to increment count, release user & bar from reentry would work as @mihnead suggested. It is super easy to setup too. However, it limits your ability to see conversions that happen later on in the session. It also isn't an option if you're using Analytics for Target (A4T) reporting. One way to handle in these scenarios is to:

1.  Add a "view banner" trackevent to the experience(s). You could do this by adding a custom modification (in VEC) with a simple script that sends a signal back to Target.

 

<script> adobe.target.trackEvent({mbox:'dataCapture', params:{'profile.activity123':'viewedExpA'}}); </script>

 

Note: The profile parameter name can be activity specific. Each experience should have a different value (e.g., viewedExpB, viewedExpC)

2.  Modify your XT experience audience(s) to include people with: visitor profile > activity123 that does NOT contains value "viewedExpA" (specific to each experience of the activity)

This is more to setup but will work with A4T and Target reporting without limiting the metrics you can report against. 

3 の返信

MihneaD
Adobe Employee
Adobe Employee
June 10, 2021

@jaredho 

Take a look at the last page in the activity editing "Goals and Settings" there shoudl be an option there "Advanced Settings" in here you would select the option titled: "Increment Count, Release User & Bar from Reentry" Let me know if you run into any further issues.


--Mihnea Docea

jaredho作成者
Level 2
June 15, 2021

Hi @mihnead, thanks for the clarity. I think the limiting factor is that reporting source has to be Adobe Target. Is there a way to keep Adobe Analytics as the reporting source will still having the option to "Increment Count, Release User & Bar from Reentry"?

ryanr7Adobe Employee回答
Adobe Employee
June 14, 2021

Hi @jaredho

It depends a little. If you are using Target as your reporting source and your goal metric is set to viewed an mbox > ** display mboxes ** then changing the advanced settings to increment count, release user & bar from reentry would work as @mihnead suggested. It is super easy to setup too. However, it limits your ability to see conversions that happen later on in the session. It also isn't an option if you're using Analytics for Target (A4T) reporting. One way to handle in these scenarios is to:

1.  Add a "view banner" trackevent to the experience(s). You could do this by adding a custom modification (in VEC) with a simple script that sends a signal back to Target.

 

<script> adobe.target.trackEvent({mbox:'dataCapture', params:{'profile.activity123':'viewedExpA'}}); </script>

 

Note: The profile parameter name can be activity specific. Each experience should have a different value (e.g., viewedExpB, viewedExpC)

2.  Modify your XT experience audience(s) to include people with: visitor profile > activity123 that does NOT contains value "viewedExpA" (specific to each experience of the activity)

This is more to setup but will work with A4T and Target reporting without limiting the metrics you can report against. 

Adobe Employee
June 15, 2021
Yes the mbox name can be whatever you choose. The key part is really just the profile parameter name and values because you'll be using those in the Audience definition. You don't really need to reference the mbox name so I tend to use something generic like 'dataCapture' in these cases.
Level 2
March 12, 2024

Is this work for taget-global-mbox and through omni channel