Versions Compared

Version Old Version 3 New Version 4
Changes made by

Men-hau Luc (Deactivated)

Romain Kalinsky (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WAM is able to ingest Proxy files for segmentation creation then activation

...

After choosing the connection, Proxy configuration need to be set

...

Fields to fill

Configuration name : Proxy name configuration

File Path : Bucket where the files are retrieved

File Pattern : YYYYMMDD-Proxy-Configurationname-label.csv

Email to notify : Email to receive confirmation of file ingestion

Separator : file separator | , ;

File compression : no/yes

Delete remote files : no/yes

Encrypted identifiers : no/yes

...

Proxy File Ingestion

 

Place file on the bucket with file pattern set on the Proxy configuration of the account

⚠ Bucket should only contain CRM files of the configuration

Header in file explanation

webo_id or
mobile_id

mobile_type

crm_id

crm_pattern

namespace_type

account _id

cs

...

webo_id|cs
webo_id|crm_id|crm_pattern|namespace_type|account_id|cs
mobile_id|mobile_type|crm_id|crm_pattern|namespace_type|account_id|cs


Rules


● We can’t have “webo_id” and “mobile_id” both present on same line

⚠ Mandatory Columns

For Mobile ID only

For CRM ID only

“mobile_id”, “mobile-type” and “account_id”

“crm_id”, “namespace_type”, “crm_pattern” and “account_id”


We must have at least 2 of these fields (webo_id, mobile_id, crm_id or cs)


● We can have at most 7 columns

● one account ID per file only

Values

“webo_id”
Can be:
● a simple webo id on 12 or 14 characters
● A crypted webo id (22 characters)

...