Hi Ishan,If you want to simply forward the string to another tool , I
think there are better ways of achieving that without causing regression
risks to your existing campaign setup. 1. Forward the logs received in
the nl6/var//redir/logs/ folder to your tool as it is or
apply some filtering commands ( awk /sed ) to only forward the data for
user_agent strings. This can be achieved by running a shell script which
will extract the lines and send only the column containing the
user_agent string. 2....
Hello Ishan, The option "NmsTracking_UserAgentRules" is used to
normalize the data present in the user agent , in a user friendly manner
, as captured in the raw tracking logs.The tracking data is normally
used to prepare and view reports by a marketer.The data present in
tracking logs on the server would not make much sense for a marketer if
presented as it is. Also , there are Out-of-box reports that depend on
the user agents data from the nms:userAgent table. So can you please
detail what oth...
Hello Ssb, All the schemas you have mentioned are following the template
of xtk:folder as evident from the below definition : You can go in the data tab for each schema , do a
configure list and select the SQL query to find out which table the
query is actually running. This basically means , nms:program ,
nms:offerCategory , nms:plan will exist as different types of entities
under the xtk:folder table ORthey are folders of different types in the
hierarchy . Regards,Adhiyan
Hello,There can be two possibilities. 1. Schemas are created but not
synced with the Database from the application via the update database
wizard.2. Certain attributes when applied to a schema ensure that they
don't get created as a table on the Database.For example - you won't see
nms:broadLog and nms:trackingLog in the database although they are
present in the console as they are libraries ( templates ) to create
other tables.the attribute - library="true" determines this. So if it's
not case ...
HelloDoing the separation via sub-folders seems to be the common
approach in this scenario as it's easier to implement. You can look into
Distributed marketing to achieve this requirement where Operators can be
grouped into Organisational unit and only entities for that Org, unit
will be visible to users.You then need to place templates in the
respective Org units. The other possibility is to create a two new
columns and add it in the delivery input form.BU 1 should have column 1
and BU 2 should...
Hello, I think you are right that it’s an access related problem.
Curious to know if the same user cab publish offers under the same
folder ? Also you can try some trial and error methods to narrow down
the issue further like : 1.Remove the user from the custom group 2.
Remove the access for custom group from the offer folder 3.Add the user
to the folder directly with rwx rights Also worth going through the
interaction.js script to see if there is any dependency on OOB named
Hello SSB, You can probably achieve this with a web form / web App's
combo box feature with visibility conditions. For example -1 >. Create a
variable and assign categories Sports and Book. Type of input should be
combo box. 2>. Then create another combo box with Product name and add
the values for sportsIn this input select the visibility condition as
var1 = Sportsexample - 3. Similarly create another combo box input for
Books and add a visibility condition var1 = Books. End result should be
Hi Scott, From your experience , What do you think are some key points
while integrating AAM with Adobe Campaign. This is one of the most
widely used integrations and also one prone to many issues.
Hello Jose, It's by design that some fields of the OOB tables are not
exposed for update via UI due to performance considerations.There are
services like MTA , web or wfserver which continuously update the OOB
technical tables like delivery logs and introducing a manual INSERT will
slow down / block the automatic process. If you can elaborate the
objective , probably we can find an alternate way.
Hi Shiva, That because of how google handles downloading of images .
When an open is tracked gmail downloads the open tracking pixel via
google image proxy but when it's a click the data does not come through
google image proxy. This is the reason of not seeing proxy for clicks