if you do add them as test1,test2,... it would rather get complex to define amd also not too easy to add new values later on. So I would rather approach it as: * No custom attributes on the profile* instead a new custom resource called cusPrrogram or so - 1 object exists per unique record (e.g. test...
Technically for your case both will do the same. The latter one is the syntax created in the Creative Designer and allows to change it more easily in the UI.The first record is rather the legacy syntax which still works
Unfortunately in dynamic reporting al you can do is to define a date range.Though this won't fit your requirements as e.g. a click might be reported on another day than the delivery. Brst guess for such aggregated numbers would indeed be a workflow: * Query activity to load the deliveries * Extract ...
Yes, best would be to create:custom resource Programanother custom resource ProfileProgramReference which contains the relation between the 2 resources
There is no function to do this directly.What you could do is an expression like:Iif(Month(<Date>)= '1', 'January', Iif(Month(<Date>)= '2', 'February', ...))
Yes, Campaign Classic can do a similar integration.Though there you do need to use a JS activity to fetch the data.As an advantage, all parsing/processing can be done in ACC, no need for I/O runtime there
The variants are not separate schema but stored as an array-type of property on the delivery.You can't access the variant properties / list in workflows