Hi, As you would have seen the documentation:
types of Transaction emails different purposes.1. Profile type should be
used when you have a unique key with you when a certain event happens
and you know t...
Hi, Based on your description there are three possibilities: 1. Your log
location is different from the default log location for Adobe campaign2.
you are not using syslogd for logs. By default, the Adobe Campaign
platform has the syslogd module installed on it, but it is possible to
use another syslog daemon. This module creates the log files in the log
directory. If you had any build or infra updates this might have
happened.3. Somehow your web.log creation is disabled. Follow this step
Hi Milan,This is happening because of your ootb data policy for the
mobile phone. You have to add a new field in the recipient for mobile
phone and update the target mapping to disable this behaviour.
Alternatively: Did you uncheck the following checkbox in the connector?
anyone of these two will fix your issue. Regards,Amit
Hi Nitin, You should use scheduler available within the incremental
query activity.If this is not possible for some reasons then you can use
scheduler +JS to keep track of the last execution date and a standard
query activity to use that execution date from JS in a workflow.
Hi Anumol, What you are observing here is, how Adobe campaign Tracking
works.Read this excerpts: Personalization and tracking process
overviewFor tracking detection, Adobe Campaign embeds Tidy to parse the
HTML source and detect the pattern. It lists all the URLs of the content
so that they can be tracked individually. Adobe Campaign uses Tidy again
to replace the URL (http://myurl.com) with a URL pointing to the Adobe
Campaign redirection server.For example, in the initial content:
Jayesh,In the traditional email it's not possible but using AMP it will
be possible for major ISPs.Adobe campaign added support for AMP for an
email in the recent build so you can use AMP 4 Email to achieve your
Hi,Jon recommends a way which will work for you but Personalisation
blocks are not designed to include the Js objects in Deliveries. You
should use the following method to include the Js.This will Add your Js
object into your execution context similar to what load library does. in
delivery you can use something like: <% eval( bigint.data ) ; %>