WAM is able to ingest Offline files for segmentation creation then activation
Goal = Simulate online hits based on a Weboid and a datalayer
After choosing the connection, Offline configuration need to be set
...
Fields to fill
Configuration name : Offline name configuration
File Path : Bucket where the files are retrieved
File Pattern : YYYYMMDD-Offline-Configurationname-label.csv
Email to notify : Email to receive confirmation of file ingestion
Separator : file separator | , ;
Namespace pattern : Offline pattern set in WAM
Identifier Label in file : Offline in the Offline file ingested
File compression : no/yes
Delete remote files : no/yes
Encrypted identifiers : no/yes
Offline File Ingestion
Place file on the bucket with file pattern set on the Offline configuration of the account
⚠ Bucket should only contain Offline files of the configuration
File header
must contain Weboid and datalayer columns
...
The offline datalayer simulates a collect hit by associating a weborama identifier and key values with keys being the column header.
When the file is being processed, every row of the file is read as a collect hit and challenge the custom segment rules of the namespace set in the file import configuration.
The file must be a csv format and include the csv extension, while the content of the file must include the header which should start with the column “webo_id'. All other columns are customs. However the delimiter used in the csv file must be the one declared in the configuration.
for instance, with a configuration having a pipe as a separator, the content should be similar to:
...