Adobe Target | Community
Skip to main content

Adobe Target

Welcome to the Adobe Target Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Target.

  • 4,186 Total posts
  • 7,054 Total replies
4186 Total posts
chandut028
chandut028New Participant
 Adobe Target
J
jimy24431669New Participant
 Adobe Target
nitins96420484
nitins96420484New Participant
 Adobe Target
venkatg72087904
venkatg72087904New Participant
 Adobe Target
jaykwon
jaykwonNew Participant
 Adobe Target
zhengquanz32073
zhengquanz32073New Participant
 Adobe Target
A
alissonxavier01New Participant
 Adobe Target
W
walmarNew Participant
 Adobe Target
JonMaguire
JonMaguireNew Participant
 Adobe Target
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target Activity Audience AccessibilityNew

While setting up the audience for a Target activity, the experience cloud interface provides two options (create audience under) – 1. Audience Library or, 2. Activity-Only Audience.It would be instrumental to add a new option while dealing with audience creation for your Test where user can move the audience from ‘Activity-Only Audience’ group to the ‘Audience Library’.This feature will be helpful in case user inadvertently creates audience under ‘Activity-Only Audience’ for a Test setup and later realizes that the created Audience will also be utilized by other Target Test Activities. In this situation, user looks for some option that will make this task easy to move their audience from ‘Activity-Only Audience’ to ‘Audience Library’ which will ultimately set this audience available to other Target Activities.Current interface only facilitates with a flow of actions where user might have to delete this audience from ‘Activity-Only Audience’ list and then will have to recreate it under

3
38001
MihneaD
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target: Why DOCTYPE is important for your Webpage

Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-compliant parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends o

27030
Khushboo_Kalia
KelseyTaylor
KelseyTaylorEmployee
 Adobe Target
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target: Why DOCTYPE is required on the webpage

Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-compliant parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends o

22980
Khushboo_Kalia
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target: Why DOCTYPE is required on the webpage

Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-compliant parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends o

23610
Khushboo_Kalia
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target: Why DOCTYPE is required on the webpage

Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-compliant parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends o

24230
Khushboo_Kalia
V
vinodh_dinakar2New Participant
 Adobe Target
A
analytics_unionNew Participant
 Adobe Target
Khushboo_Kalia
Khushboo_KaliaEmployee
 Adobe Target
Adobe Target: Why DOCTYPE is required on the webpageNew

Missing DOCTYPE declarations often disables the Adobe Target library on the webpage, without which the personalization is not possible on your site pages. Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-complaint parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends on some JS APIs w

0
20170
Khushboo_Kalia
Vikaz
VikazNew Participant
 Adobe Target
D
dradyukNew Participant
 Adobe Target
DaveDigital
DaveDigitalNew Participant
 Adobe Target
Live Target activity dashboard with A4T

Has anyone advice or experiences you can share around creating a shareable dashboard view of live test KPIs - ideally through native Adobe tools, but will also consider API integration? As our volume of activities grow, current methods of manually transferring into other tools for reporting is making daily /weekly monitoring and maintenance a an ever growing overhead and we need a more efficient process. Have looked at various third party tools to ingest the API  ( e.g. Iridon) but all seem to have flaws in the process in one way or another. I may be aiming too high to have XTs, A/B tests and automated activities available together - but at it's simplest I am simply attempting to produce a dashboard view of A/B tests with clear indicators of current performance with conversion and behavioral KPIs from the Adobe Analytics.  I hope this is not too general a question, but am hoping fellow clients have faced and resolved similar challenges with sharing test da

16710
DaveDigital
R
RounakKumarNew Participant
 Adobe Target
I
inquiztrNew Participant
 Adobe Target
How to setup staging permissions in Target

What I am trying to achieve is give our business team permission to create/edit/delete and activate rules for only our staging environmentexample : staging.site.comThen when they have finalized their tests, have other person activate it for live production environmentexample: site.com Currently we had to deny 'activate' rights to them because of the risk of harming production. The down side is I have to activate/deactivate their rules 15 times a day while they develop them. (their rules are manually configured restrict to our staging site). Am I missing something? There must be a better way for the team to test their rules without having to ask me to activate it? If i give them permission to activate, then I can not guarantee that they wont abuse that privilege push to production without IT being aware (and potentially causing a site outage). 

32531
MihneaD
O
oliverf82757722New Participant
 Adobe Target
Authenticating an event webhook from the hash of the body

https://www.adobe.io/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/intro/webhook_docs_intro.md#authenticating-events At the bottom of this page there is a small example of "Javascrip(pseudo-code)" which is entirely unhelpful as it fails to explain the only part of the code that is important to know. Where/how do you get `raw-request-body` from?At the moment my code looks like... const validateClientSecret = (req: any) => { const secret = secretKey(); const hmac = crypto.createHmac('sha256', secret); hmac.update(req.body.toString()); const hash = hmac.digest('base64'); if (req.header('x-adobe-signature') !== hash) { // other stuff here... return false; } return true; };  If I pass in just `req.body` it throws an exception as `body` is the wrong type. If I use `req.body.toString()` it creates a has but not one matching the header value.Can someone help me as I'm now not sure if I'm using the right value and ch

10880
O
C
CorralesDNew Participant
 Adobe Target

Badge winners

Show all badges
Terms & ConditionsAccessibility statement

Loading footer...