I believe this is standard now for the platform. When we initially
adopted ACS the term used to be longer, but since GDPR has come into
play they have reduced it to 6 months.You could set up a scheduled
workflow to export the data on a monthly basis and then use that data
outside of ACS to store all logs if you need to reference history older
than 6 months.
To export a list you need to have an SFTP server available or an AWS
account. You are unable to export a file directly to your local
machine.Once the file has been exported to the SFTP area, you can access
that file and save a local copy if required.In terms of the fields you
need - You specify these within the extract file activity.
Currently we import a large number of stand alone lists into ACS and
save these as an Audience (Type: List).When you go into each Audience,
it has a number count, and a 'Count Date' listed. Unfortunately that
'Count' number doesn't automatically update - it's a static number that
relates to the original number of a list. The count date seems to update
each time that audience is used for a mailing, but by looking at it, it
suggests that the count number, would relate to the count date, which is
I've noticed the count function is available if you add Additional data
to a query from an alternative data schema, but I'm not sure how to make
this work for the native(profile) schema.We'd find this functionality
useful too so I'm keen to find out if it's possible too.
In the Load File activity it would be very useful if you could set your
own default values for fields within the 'Column Definition'
tab.Currently every time we load a new list and refresh the file
structure, all of the field values within Column Definition are reset to
the default settings, so every time we need to manually go in and set
one of the fields to an Integer type, and set another field to convert
all values to lowercase (for the email address).This leaves scope for
user error if anyo...