@LaurentLam I am trying to implement something similar but via
personalisation block. The problem is I am not able to read my xml
stored in a memo data type variable in Personalisation block.It always
give me empty value.<% var rate =
targetData.rawDatadocument.write(rate);%>and if try to refer to child
nodes, it says targetData is 'undefined'<% var rate =
targetData.rawData.person.discount;document.write(rate);%>Could you
please help me if I am missing anything? Thanks
@LaurentLam I was just reading through this thread, just wanted to
verify does using a continuous or recurring delivery activity impact any
retargeting that may occur via AA triggers?
No, as the webTracking tag has been designed in order to track what
recipients are doing on the website after clicking in the email.For your
need, you cannot use this approach and more rely on different solutions
such as AEM / google analytics / mix panel / etc
Not sure to understand fully the need.On my side, I prefer to use an
array in JSON and to loop directly in the delivery in order to build the
HTML:javascript is prohibited in emails, at least, for deliverability
purpose
Hello @Luca_Lattarini ,Best practice is to just "import" required
data.There are 3 main reasons:1- performance is better on your local
database: your WKF will 2- when you create a schema (so queryable)
through FDA, there is a lot of intrusive objects that are created on the
external database a- AC will have to create the OOTB AC Stored
Procedures (in order to have the query expressions to work) b- AC will
also create work tables (WKFxxxxxx) on the external DB when running a
workflow that involve...
I've changed my approach given the issues faced with using
personalization blocks and now everything is working correctly. Given
that I still required a centralized repo, I used platform options to
store the utm logic And since my templates were being generated on the
back of an API call using content templates, I decided to execute the
logic stored as string on the platform options in during the generation
of the publication template. var x = getOption("utm_privateclients");
var utm = Function(...
The change in the deployment wizard will not affect existing deliveries
but only the new templates created (templates will herit from the new
default value).Once you'll have templates with the new value, all
deliveries created from those templates will then pick this value.The
other way is to create a typology rule (of type "Control" and "at the
start of targetting") using in the JS:myVar =
getOption("myOption");delivery.scenario.webValidityDuration = myVar * 60
* 60 * 24;delivery.mailParamater....
Thanks for the replies @Darren_Bowers and @LaurentLam, it's good to be
aware of potential pitfalls. The main use for the auto restart would be
for technical work flows which load data from external systems. The
process would be limited to selected work flows and would generate an
alert to our support team.
Hi @Shane0806 ,Unfortunately there is no such degree of audit as AC
never handeled natively versionning.Here how you can investigate on an
issue:0- try to know when the modification arrised1- if the "modified
by" and "last Modified" cannot be trust or found on the objects that
have been modified, you can play to Sherlock Holmes by analysing the
"logins.log" file on the server: Log files | Adobe CampaignIt contains
every logins that try to log on the server with the timestamp (and even
the IP if ...