Hi, it seems your event contract definition doesn't include the audience
field property.check if your event is published in your
environment.After publishing go to API preview tab and ensure that you
are using the exact definition from there while invoking the API
call?Check if you are using any incorrect personalisation in your HTML
Hi follow given steps: 1. add a false collection to your base query
using additional data. 2. add enrichment to compute your aggregates:3.
in your enrichment go to Advanced Relations tab and add a relation to
your collected added in the previous query using the @collectionLink as
the source and destination expression.4. Using additional data in
enrichment add your aggregates:now you can use this CountRecords in your
email using personalisation field. Regards,Amit
yeah, it's a shame. The Restrict to information found in sub-folders of:
option lets you limit the rights attributed to the operator of a folder.
Only the subfolders of the node specified in this option will be visible
to the user in console. so it will not work for JSSP page.
Hi Milan, You have to increase the stackSizeKB to at least 1024 KB. Go
to your server configuration and do the following Do check with support if hardware support 1024 at
stack size. What Are the Side Effects of Raising the Stack?Raising the
default system stack size by definition allows for larger stack segments
for every process on the system. If swap space on the system is near
capacity, raising this tunable will increase the amount of swap that is
reserved for each process. This would allo...
if you still wants that method then you have to create another schema
for monitoring if you want ACC to handle everything in-house. every time
there is an invocation to this JSSP page you can create a row there. and
log the bytes requested as response and session info.
There is a problem as soon as you give the access to JSSP page, they
will automatically get access to SOAP. then the only way you can achieve
this is by hard coding the access in JSSP for the user using
logonEscalation method or something similar.
Hi Szymon,In your use case, you should not allow any user to login to
Adobe campaign as Jon mentioned there are couple of security concerns
when you allow a user to login to your marketing database even via API.
The recommended way will create a middleware API(for this particular
microservice) endpoint which should act as a bridge to your system from
the outside world. Cheapest way will be to use Amazon lamda based
function where you can easily measure the data usage and at the same