Adobe Target

Hello @kdesousa When Analytics audiences get published to Experience Cloud, they then become available for use in in Target tests. These audiences do have an update delay up to 24 hours, so if a visitor qualifies for the audience during a session, then target activities will not get served to them until a subsequent visit. You can get around this lag by building audiences in Core Services audience library off of Analytics Attributes

core services audience library can be built off of analytics attributes. This link speaks to uploading custom attributes, but it does show how to navigate to the Audience library through the People option in EC menu:

What Are Customer Attributes and How Do I Use Them? | Adobe Target

As for non-logged in users, they can be targeted based on behaviors tracked on their device browser as long as the cookie has not been reset manually or due to ITP 2.1. You can use mbox parameters to capture important behavioral targeting dimensions and mbox events for conversion points:

Custom Parameters: Can I Target Visitors Based on Custom Parameters? | Adobe Target

Target Events: Event tracking | Adobe Target

Can I Create an Audience to Use Only Once? | Adobe Target

Hey @EmilyDa4,

I'm going to break up my responses. Hopefully I'm follwing your questions correctly.

1) So I recommend people optimize a page in a fashion that will help them know where to test next. I recommend starting with presence test (what belongs/doesn't belong). Then location testing (of what belongs where on the page does it belong). Then after that function/style testing. This should help you focus on the parts of the page that are most impactful first. A presence test can also give you a sense for the range of impact for the different elements, allowing you to focus on the most impactful elements first.

Hello @EmilyDa4 Responding to:

 3.can you build custom audiences off of specific user based actions? / is this a recommended approach? i.e. only show X CTA button to users who abandoned the form page

Yes, specific user-based action targeting creates significant value and gets commonly used still by customers with a wide array of testing maturity. The main requirement will be to track the desired targeting behaviors to then use within testing. Adobe documentation details steps recommended to perform behavior-based targeting:

Custom Parameters: Can I Target Visitors Based on Custom Parameters? | Adobe Target

Target Events: Event tracking | Adobe Target

Can I Create an Audience to Use Only Once? | Adobe Target

2) When you have multiple audience types that you anticipate could behave differently, I would still run my AB test as normal but adding in applicable audiences for reporting. Then when evaluating the results I'd look at the results with all visitors, then for each of the other audience types. Keeping in mind if those audiences are small they may not reach significant/meaningful results. So you have to keep in mind your number 4.

4) I recommend that you use the test duration calculator. This help doc describes it: https://experienceleague.adobe.com/en/docs/target/using/activities/abtest/sample-size-determination

In short you need to have an adequate amount of visitors and conversions before the "confidence" measures showing in Target or Analytics are truly meaningful. This amount also would apply if you are looking at a slice of the audience.

Hi @SamLe2,

Audiences shared from Analytics to Target can range in their lookback windows. The look back isn't just based on their last visit but when they qualified for the behavior you are defining the audience on. So if your audience is for people that click a Learn more button on your site they would have completed that behavior in the last X days from when they are getting qualified in the Target activity. Remember Analytics shared audiences are update at least daily in the Experience Cloud and Target.

>>So if your audience is for people that click a Learn more button on your site they would have completed that behavior in the last X days from when they are getting qualified in the Target activity.

If the person clicked the Learn More button (tracked in analytics) more than 90 days ago, would they still qualify for the Target segment?   If the person clicked the Learn More button button more than 180 days ago, would they still qualify for the Target segment?

They would fall out of the audience after the behavior has moved passed the window. The look back window is configurable to different durations: 30, 60, 90, 180 (if I remember correctly). More info: https://experienceleague.adobe.com/en/docs/analytics/components/segmentation/segmentation-workflow/s...

Hello hgomattam! 
Implementing category affinity should not impact page performance. Are you finding that the page performance is being impacted as a result of implementing category affinity? Please share any additional/specific details regarding the behavior you're encountering.

Hello!
I am making a trackevent with a code that would look at the page level elements to track the category. Also, running this as an activity on target. What is the best place to include this code that would look at the page elements? We do not use Launch.

Hi@hgomattam,

So if you are using a trackevent to capture the page category info for the category affinity profile, that should work fine and not impact page performance because a trackevent is a non-blocking call and can be fired at any point during the page load. This should also work fine for category affinity use cases because category affinity is something that is usually used after they have been on a page that populates their affinity. It's often used when they come back at a later time and you want to personalize a message based on their "favorite" category. Here's the help doc on it: https://experienceleague.adobe.com/en/docs/target/using/audiences/visitor-profiles/category-affinity

Sorry using my proper profile now.

Hello yeswin1,

There are multiple ways that images can be changed when using the VEC (Visual Experience Composer) in Target.

One way would be to edit the HTML itself. Please see the "Text/HTML" section of the "Visual Experience Composer options" documentation found via the URL below:
https://experienceleague.adobe.com/en/docs/target/using/experiences/vec/viztarget-options#edit-text-...

Another way would be to use the Replace Content function. Please refer to the "Image" section of the "Visual Experience Composer options" documentation via the URL below:
https://experienceleague.adobe.com/en/docs/target/using/experiences/vec/viztarget-options#image

Note: Swapping images requires an Adobe Scene7 (Dynamic Media) Account. A free account can be requested by submitting an Adobe Target Support ticket.

With regards to the issue with "flicker", there are multiple ways to manage this, depending whether you use Tags/Launch. Please review the documentation that matches with your scenario:

How at.js manages flicker
https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/at-...

Target Pre-Hiding Snippet
https://experienceleague.adobe.com/en/docs/platform-learn/implement-in-websites/implement-solutions/...

Hello @MelBe1 ,

Very good question; it gets right to heart of what it takes to scale experimentation and use your testable traffic effectively.

The slider will be the easiest way to prioritize one test over another for the same location and audience.

The option to create a new audience with an exclude condition on in other tests helps to completely isolate on test from all others occurring on the site if there's any concern for their potential impact on this one.

Solved: Audience - Visitor Profile - Not in another test |... - Adobe Experience League Community - ...
Profile scripts come in when more complex inclusion/exclusion rules need to be defined. Ryan Roberts here tackled this scenario in this thread:
Mutually exclusive - Adobe Experience League Community - 238965

Hi @niocolasmeriel,

Is this for an AB test? I would suggestion using "multiple auidences" to handle different different languages and different currencies. You need a way to signal to Target that a user is on one language vs and other, but when you are passing that info you can create language based audiences and then create versions of the experiences of the test that still maintain the essence of what you are changing but properly reflect the different langauges/geos you want to include in the test. Here's the help doc with some additional info on it: https://experienceleague.adobe.com/en/docs/target/using/activities/abtest/create/target-experience-t...

Hi @yeswin1,

I have found that it is not uncommon for lift to shift over the life of an activity, especially in the first week or two. The amount of shift is going to be variable of course and depends on volume of traffic, degree of changes in the test, and audience behaviors.

Also, I recommend using our test duration calculator to help you determine when a result is conclusive. Help page here https://experienceleague.adobe.com/en/docs/target/using/activities/abtest/sample-size-determination. Lift moving is exactly the reason it is important that the test runs until a sufficient amount of traffic is included in the test. It is only after that amount has been reached that "confidence" levels in the test report can be reliably trusted. Otherwise, you are more likely to have false positive scenarios.

This still would apply to a test using Auto Allocate. Keep in mind Auto Allocate isn't trying to "pick" the winner earlier, it's trying to get more traffic to the competitive experiences faster than an even split does. It works best in AB tests with 3 or more experiences. It helps you get to the sufficient amount of traffic quicker by limiting traffic to experiences that don't appear to be likely winners.

Hi @CocoNYC13615,

Were you wanting to know how that can be used within a Target activity? I might have to watch that video later and respond later today.

Hi. We would like to know more of AEM configuration. How to do the configuration like.

• Meta tag pipeline
• AEM Article Component with Target Recommendations Toggle and specify Target Activity name

Hi @MelissaMa7,

I use FireFox most of the time so I'm still using the Adobe Target VEC helper extension. That said I haven't heard of known issues with the new extension on Chrome. I will message you directly to see I can replicate your issue.

Hi @MelissaMa7,

It should only apply to new reporting from that point forward for Target reporting. However, if you have Target reporting in Analytics or CJA you could apply a retroactive filter there to see results that exclude certain IPs on prior tests.

Okay good to know. Thank you so much!