The main data types in Agillic are Person Data, One-to-Many Data, Global Data Tables, and Global Data. Each type serves a slightly different purpose. To upload different data types, you will need to format your import files differently.
This article runs through the different data types and how you can upload them to your Agillic instance.
Person Data
Person Data is data that’s specific to each recipient such as their first name, email address, date of birth, or favourite product.
Person Data is only ever a single value. If there is more than one value - for example, a recipient’s recent purchases - then it is classified as One-to-many data instead.
The Person Data Format
When importing Person Data, the first column must include a unique identifier of each recipient. This might be their email. Then, each of the following columns must contain the other Person Data you wish to import. These columns can be given in any order.
A Unique identifier can be any Person Data, which has been set to be unique.
Unique Person Data fields have a flag icon next to them
In the example below, we are using the recipient's email as the unique identifier.
| MOBILE | FIRSTNAME | AGE | FAVOURITE_CANDY | EMAIL_PERMISSION | SMS_PERMISSION | |
|---|---|---|---|---|---|---|
| blue@sweetmail.com | 12345678 | Mr. Blue | 29 | Caramel | TRUE | FALSE |
| green@sweetmail.com | 23456789 | Mrs. Green | 51 | Chocolate | TRUE | TRUE |
| yellow@sweetmail.com | 34567890 | Ms. Yellow | 27 | Vanilla | TRUE | TRUE |
| purple@sweetmail.com | 45678901 | Mr. Purple | 38 | Fruity | FALSE | FALSE |
| black@sweetmail.com | 56789012 | Ms. Black | 30 | Licorice | TRUE | TRUE |
| red@sweetmail.com | 67890123 | Mrs. Red | 60 | Caramel | TRUE | FALSE |
| white@sweetmail.com | 78901234 | Mr. White | 47 | Fruity | TRUE | FALSE |
| pink@sweetmail.com | 89012345 | Ms. Pink | 19 | Vanilla | TRUE | TRUE |
Table 1: Example of a Person Data import file
Fixed Person Data
Some Person Data is fixed, meaning it can’t be altered. Examples include ‘CREATED’, ‘LAST_EMAIL_OPENED’, or ‘EMAILS_THIS WEEK’.
You can’t delete or edit Fixed Person Data fields. They can be recognised by a small padlock icon next to the name of the data field.
Inspecting the Fixed Person Data 'EMAILS_THIS_WEEK'
List of Fixed Person Data fields, and editing rights (can the value be modified).
| Name | Description | Editing Rights |
|---|---|---|
| AGILLIC_ID | An ID assigned to a recipient when created in Agillic. You can use AGILLIC_ID as a unique ID | Cannot be edited |
| CLICKS_FROM_EMAILS | The number of events triggered in emails by the recipient. |
Only via UI |
| COMPLAINT | If the recipient has marked the email as spam using the feature for this in the inbox, or by using the email-client's unsubscribe function. | Can be edited via Side Effects, API, and Import (every 6 months), and UI |
| COMPLAINT_DATE | The date and time a recipient marked an email as spam | Only via UI |
| CREATED | The date and time the recipient was added to Agillic | Not possible |
| EMAILS_OPENED_TODAY | The number of emails opened by the recipient since midnight. the counter resets every day at midnight. | Only via UI |
| EMAILS_OPENED_WEEK | The number of emails opened by the recipient during the week (Monday – Sunday). Sunday night the counter resets. | Only via UI |
| EMAILS_THIS_WEEK | The number of emails sent to the recipient during the week (Monday – Sunday). Sunday night the counter resets. | Only via UI |
| HARD_BOUNCE | The number of times an email sent to a certain recipient has hard bounced | Can be edited via Side Effects, API, and Import (every 6 months), and UI |
| INACTIVE_EMAIL | If a recipient has not opened a specified number of emails over a time period this value will be set to True. You can define the number of emails and time period under System in the Email section. If a recipient becomes active e.g. by opening an email, the INACTIVE_EMAIL Field will clear. Read more about the inactive feature here. | Only via UI |
| INBOUND | If the recipient has sent an inbound SMS using an SMS service managed by Agillic. | Only via UI |
| LAST_ACTIVITY | The last date and time any activity in Agillic took place for the recipient. E.g. a login as well as sending an SMS. | Only via UI |
| LAST_CLICK_FROM_EMAILS | The last date and time a recipient clicked in an email | Only via UI |
| LAST_EMAIL | The last date and time a recipient received an email | Only via UI |
| LAST_EMAIL_OPENED | The last date and time recipient opened an email | Only via UI |
| LAST_INBOUND_ACTIVITY | The last date and time an inbound activity in Agillic took place for the recipient. e.g. viewing a page, sending an inbound SMS or achieving an event. | Only via UI |
| LAST_MMS | Indicates the last date and time an MMS was sent to the recipient. | Only via UI |
| LAST_OPEN_CLIENT | Which type of client was used to open the last email. The "Other" category will capture all minor clients. | Only via UI |
| LAST_OPEN_DEVICE | Which type of device the last email was opened from. The options are Desktop or Mobile. | Only via UI |
| LAST_OUTBOUND_ACTIVITY | The last date and time an outbound activity in Agillic took place for the recipient. E.g. receiving an SMS or email. | Only via UI |
| LAST_PUSH | Set to current time every time the recipient received a Push Notification | Only via UI |
| LAST_SMS | The last date and time an SMS was sent to the recipient. | Only via UI |
| LAST_UPDATED | Set to current time every time any non-fixed person data updates. This doesn't include changes to One-to-many data. | Only via UI |
| LAST_USED_APP_FOR_EMAIL | Which application or browser was used to open the last email. Note: Some apps register as a browser. | Only via UI |
| MALFORMED_EMAIL | Used to flag a recipient email as malformed if it is not valid. E.g. recipients with "@hotmail.cooom" or other invalid top level domains will get this flag. Agillic checks Recipients when imported. Malformed will also be set if the domain is unavailable (Ping failed) | Only via UI (by changing EMAIL value) |
| MMSS_THIS_WEEK | Only via UI | |
| MSISDN_TYPE | If a recipient has a malformed mobile number this value will be set to 'Invalid'. Otherwise it is set to one of pre-defined types. The value is re-evaluated when mobile number is changed or system settings related to mobile number are changed. | Only via UI |
| OPERATOR | The name of the operator, if a recipient has sent an inbound SMS using an SMS service managed by Agillic. | Only via UI |
| OUTBOUND_THIS_WEEK | The number of outbound communication (emails, SMS, MMS, WAP Push) sent to the recipient during the week (Monday – Sunday). Sunday night the counter resets. | Only via UI |
| PUSHES_THE_WEEK | The number of Push Notifications sent to the recipient during the week (Monday – Sunday). Sunday night the counter resets. | Only via UI |
| RANDOM | A random four-digit number in between 0 and 1 assigned to all recipients. You can use the number for various testing and random dividing of recipients. | Only via UI |
| SMS_THIS_WEEK | The number of SMSs sent to the recipient during the week (Monday – Sunday). Sunday night the counter resets. | Only via UI |
| SOFT_BOUNCE | The number of times an email sent to a certain recipient has soft bounced | Only via UI |
| UNSUBSCRIBE_DATE | The date and time a recipient achieved the Unsubscribe event | Can be edited via Side Effects, API and UI |
| UNSUBSCRIBED | If the recipient has unsubscribed using the fixed Unsubscribe event. | Can be edited via Side Effects, API and UI |
| VALID_EMAIL | After a certain number of hard bounces, soft bounces or when an email address appears malformed or empty during email sending, Agillic marks the recipient's email as being invalid by setting this value to False. It is important to note that if an email address is invalid due to a non-existing domain name, VALID_EMAIL is not set to False until after a small period of time from first seeing the domain. If the email is reset or if Agillic detects that the recipient has opened or clicked an email, the value changes to True. | Only via UI and Import |
One-to-Many Data
One-to-Many Data is also specific to each recipient. However, One-to-Many Data is used when there is more than one value of data to be stored. For example, a recipient’s recent purchases or subscriptions are stored as One-to-Many Data.
The One-to-Many Table Format
When importing One-to-Many Data, the first column of your upload table should be a unique recipient identifier such as email address or customer number. In the second column, insert an ID-column for the One-to-Many Table.
|
EMAIL
|
PURCHASES.ID
|
PURCHASES.DATE
|
PURCHASES.PRODUCT_ID
|
PURCHASES.STORE
|
| blue@agilliccandy.com | 1 | 01.02.2016 | 21 | Berlin |
| blue@agilliccandy.com | 2 | 31.12.2016 | 32 | Copenhagen |
| green@agilliccandy.com | 3 | 18.10.2016 | 6 | London |
| green@agilliccandy.com | 4 | 15.03.2017 | 18 | Berlin |
Table 2: Example import file structure for a One-to-Many table entitled 'PURCHASES'
Global Data Table
A Global Data Table is typically used to store content that is not recipient specific. This could be Publication data, product data, or brand data.
Global Data Tables are only intended for public non-personal data e.g. product information. Be aware that recipient specific data in Global Data Tables could lead to GDPR issues for you as a data controller. Recipient specific data has to exist either as Person Data or One-to-Many data.
The Global Data Table Format
Unlike Person Data and One-to-Many Data, you will not need the unique recipient identifier to import to a Global Data Table. However, you will need a unique row ID in the first column.
|
PRODUCT.ID
|
PRODUCT.CATEGORY
|
PRODUCT.NAME
|
PRODUCT.DESCRIPTION
|
PRODUCT.RANK
|
| 1 | Fruity | Fruity Bubble Gum | The sweet and fruity Bubble Gum will give you a long-lasting taste of fruity goodness that is sure to POP! | 1 |
| 15 | Liquorice | Liquorice Bubble Gum | The sweet taste of our liquorice Bubble Gum will give you a long-lasting taste of liquorice goodness that is sure to POP! | 2 |
| 16 | Chocolate | Chocolate Butter Scotch | This family favourite classic with a chocolate filling is sure to bring back sweet memories, indulging in the chewy caramel and rich chocolate taste | 1 |
| 2 | Caramel | Caramel Butter Scotch | This family favourite classic is sure to bring back sweet memories, indulging in chewy caramel delights | 2 |
| 17 | Vanilla | Vanilla Butter Scotch | We’ve added the best Bourbon-Madagascar vanilla to the classic, making it the newest and sweetest addition to the Butter Scotch family. | 2 |
| 3 | Fruity | Fruity Candy Cane | An oldie but goldie on the candy scene, this iconic pepperminty sweet treat is a symbol of our favourite thing: Candy! | 2 |
| 4 | Fruity | Fruity Candy Floss | Light as air, sweet as the smiles of babies - this Candy Floss might best be described as a piece of those pretty pink clouds as the sun rises! | 2 |
| 18 | Vanilla | Vanilla Candy Floss | This Candy Floss might best be described as a piece of those clouds moving by on a summer day! Add vanilla, and you’ve got a little piece of Heaven. | 2 |
| 19 | Caramel | Caramel Chocolate Bar | Made from the finest Ecuadorian beans, this 85% Dark Chocolate Bar is the perfect indulgence - it’s said to be healthy too! | 1 |
| 5 | Chocolate | Chocolate Chocolate Bar | At home or on the go, the Chocolate Bar is a sweet treat that melts on the tongue and is sure to lift your spirit! | 1 |
Table 3: Example of a Global Data Table import file
Global Data
Global Data is single value data which isn't linked to a specific recipient. It might include individual product names or the day of the week.
Fixed Global Data
Fixed Global Data is data which can't be changed. It includes the day of the month, day of the week, and the year. Like Fixed Person Data, pieces of Fixed Global Data are updated automatically by the system, and cannot be deleted or edited.
Activity Data
Activity Data is data is information on how recipients have interacted with your communications. It includes info such as whether an email soft bounced, how much activity occurred on a web page you're tracking, and the time a recipient was added to a Facebook Custom Audiences group.
You can export Activity Data to analyse the performance of your communications. For each Activity Data type, different information is given when you export it. You complete an Activity Data Export by going into the Data module, clicking the icon in the top left corner, and then selecting 'New Activity Export'.
When creating an Activity Export, each item you select will create its own file. Each of these files will have their own format.
| CUSTOMER_ID | Flow | Step | Template | Communication status | Communication timestamp | Event | Subject line | Error | Flow execution id (optional) | |
|---|---|---|---|---|---|---|---|---|---|---|
| 22fc8490-1812-4a36-b966-4040b46e1d6a | black@sweetmail.com | Welcome Flow | Send Welcome Email | Signup Confirmation | ERROR | 21.05.2017 13:18:06 | This customer has a malformed email address | 20051 | ||
| 22fc8490-1812-4a36-b966-4040b46e1d6a | Welcome Flow | Send Welcome Email | Signup Confirmation | HARD_BOUNCE | 21.05.2017 13:18:06 | This customer has an invalid email address | 20051 | |||
| 56911f59-efc0-403c-b66a-f7fc5ecbe553 | blue@sweetmail.com | Welcome Flow | Send Welcome Email | Signup Confirmation | SUCCESS | 21.05.2017 13:18:06 | 20051 | |||
| 56911f59-efc0-403c-b66a-f7fc5ecbe553 | Welcome Flow | Send Welcome Email | Signup Confirmation | READ_ACK | 21.05.2017 13:28:06 | 20051 | ||||
| 56911f59-efc0-403c-b66a-f7fc5ecbe553 | Welcome Flow | Send Welcome Email | Signup Confirmation | EVENT | 21.05.2017 13:28:36 | Unsubscribe | 20051 | |||
| 56911f59-efc0-403c-b66a-f7fc5ecbe553 | Subject Line Test | Send Email | Subject Line Test | SUBJECT_LINE_TEST | 21.05.2017 13:28:36 | Get a cool ice cream today! | 20051 | |||
| 56911f59-efc0-403c-b66a-f7fc5ecbe553 | Subject Line Test | Send Email | Subject Line Test | SUBJECT_LINE_WINNER | 21.05.2017 15:28:36 | The best ice cream in town | 20051 |
Format Explained
Recipient ID - The Recipient ID of the person who received the email. The Recipient ID will only be listed if the recipient exist within Agillic. If the recipient is deleted this value will be left blank.
Email - The email address of the person who received the email. This value is shown only if the Communication Status is either 'ERROR' or 'SUCCESS'.
Flow - The name of the Flow which sent the email. A maximum of 255 characters will be shown here.
Step - The name of the Step, which sent the email. A maximum of 255 characters will be shown here.
Template - The name of the email, as it appears in the Content Designer at the time of exporting. If you have changed the email name after exporting, you will not be able to find it in the Content Designer, unless you know its new name. A maximum of 255 characters will be shown here.
Communication Status - How the recipient interacted with the email.
- SUCCESS signifies that Agillic has successfully sent the email to the email gateway.
- ERROR signifies that Agillic failed in handling the Email Step correctly. The Error message column shows the reason Agillic couldn't handle the email correctly.
- SOFT_BOUNCE signifies that the email has soft bounced. In such a case, the receiving email server rejects the email because the inbox was full or the email server was busy.
- HARD_BOUNCE signifies that the email has hard bounced. In such a case, the receiving email server rejects the email because the email address was invalid. This means the domain does not exist or the email address is not recognised on the domain.
- EVENT signifies that the recipient clicked in the email. The 'Event' is described here.
- READ_ACK signifies that the email was opened.
- COMPLAINT signifies that the recipient clicked the 'Complaint' button for the email.
- COMPLAINT_WITHDRAWN signifies that the recipient clicked the 'Not spam' button for the email.
- LIST_UNSUBSCRIBE signifies that the recipient clicked the 'Unsubscribe' button for the email.
- SUBJECT_LINE_TEST shows the subject line of the email if the recipient was part of the test phase of a subject line test.
- SUBJECT_LINE_TEST_WINNER shows the subject line of the email if the recipient was part of the post-test phase of a subject line test.
- ALTERNATE_SUCCESS_ON_MANUAL shows that the email was sent as an alternative sending method as well in an email step.
Communication Timestamp - The date and time of the email actions such as when it was clicked or read.
Event - The name of the event clicked in the email by the recipient. This value is shown only if the Communication Status is 'EVENT'.
Subject Line - The subject line of the email sent. This value is shown only if the Communication Status is 'SUBJECT_LINE_TEST' or 'SUBJECT_LINE_TEST_WINNER'.
Error Message - The reason why Agillic could not process the email successfully. It contains information about when the Agillic Processing status is 'ERROR'.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Transactional Email
Transactional email is created as a separate activity export but have identical format to the email format explained above.
SMS
| Mobile | Flow | Step | Template | Gateway status | Gateway timestamp | Message parts | Error message | Flow execution id (optional) | |
|---|---|---|---|---|---|---|---|---|---|
| red@sweetmail.com | 67890123 | Signup SMS | Link to Signup | signup | success | 21.05.2017 14:33:51 | 1 | 40048 | |
| green@sweetmail.com | 23456789 | Signup SMS | Link to Signup | signup | success | 21.05.2017 14:33:51 | 1 | 40048 |
Format Explained
Recipient ID - The unique ID of the recipient who received the SMS.
Mobile - The phone number of the recipient who received the SMS.
Flow - The name of the Flow which sent the SMS.
Step - The name of the Step which sent the SMS.
Template - The name of the SMS as it appears in the Content Designer and the time of exporting. If you changed the SMS name after exporting, you won't be able to find it in the Content Designer unless you know its new name.
Communication Status - How the recipient interacted with the SMS.
- Success signifies that the message has been successfully sent to the gateway. This usually means that the message has been delivered to the phone too.
- HANDSET signifies that the message has been successfully delivered to the phone, meaning that we got both a successful reply from the gateway and the mobile provider or phone.
- ERROR signifies that the SMS was not sent correctly to the Gateway. It is likely that the recipient did not have a phone number, although an error in the gateway connection will also cause this status. The recipient has not received the message.
- SOFT signifies that the message submission to the operator has been successful, but delivery has not yet been possible.
- HARD signifies that the message couldn't be delivered which can happen both on or after delivery to the gateway.
Communication Timestamp - The date and time of the message was delivered to the gateway.
Message Parts - It contains the total number of messages sent to the recipient. Will show more than '1' if split up in several messages due to longer content. An SMS will normally split into two parts after 160 characters.
Learn more about how SMS characters are calculated here.
Error Message - The reason why Agillic could not process the SMS successfully. It contains information about when the Agillic Processing status is 'ERROR'.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Event
| Event | Channel | Template | Event timestamp | Counter | Promotion | Proposition | Flow execution id (optional) | Context | |
|---|---|---|---|---|---|---|---|---|---|
| red@sweetmail.com | Ice cream discount | Newsletter Week 01 - Basic Email | 21.05.2010 17:37:56 | 1 | 20056 | ||||
| red@sweetmail.com | Ice cream discount | Newsletter Week 01 - Basic Email | 21.05.2010 17:38:09 | 2 | 20056 | ||||
| green@sweetmail.com | Ice cream discount | Newsletter Week 01 - Basic Email | 21.05.2010 17:38:14 | 1 | 20056 | ||||
| Signup page | Web | Unsubscribe | 21.05.2010 18:03:23 | 1 | -1 |
Format Explained
Recipient ID - The unique ID of the recipient who achieved the event.
Event - The name of the event.
Channel - The channel the event happened through. It could be email, SMS, push, web, mobile, advisor, web service, API, print, or inbound SMS.
Template - The name of the item in which the recipient achieved the event.
Event timestamp - The date and time when the recipient achieved the event.
Counter - The number of times the recipient achieved the event unless the event has a reset.
Promotion - The name of the potential promotion the recipient achieved the event through.
Proposition - The name of the potential proposition the recipient achieved the event through.
Flow execution id - This contains the unique Execution ID to which the execution belongs.
Context - The context in which the event was triggered. Can contain context relations to GDT, OTM, Lookups and Promotions.
Promotion
| Promotion name | Proposition name | Evaluation timestamp | Template | Channel | Proposition priority | Flow execution id (optional) | |
|---|---|---|---|---|---|---|---|
| black@sweetmail.com | Split Test | Variant A | 25.05.2017 11:21:05 | Split Test - Promotion | 1 | 20051 | |
| green@sweetmail.com | Split Test | Variant B | 25.05.2017 11:21:05 | Split Test - Promotion | 1 | 20051 | |
| blue@sweetmail.com | Split Test | Variant C | 25.05.2017 11:21:05 | Split Test - Promotion | 1 | 20051 |
Format Explained
Recipient ID - The unique ID of the recipient who was exposed to a Promotion.
Promotion name - The name of the Promotion the recipient was exposed to.
Proposition name - The name of the Proposition the recipient was exposed to.
Evaluation timestamp - The date and time the recipient was exposed to the Promotion.
Template - The Email, SMS, or page name where the Promotion was exposed.
Channel - The channel used to display the Promotion/Proposition.
Proposition priority - The position of the Proposition, as ranked by priority. Each Promotion can contain different Propositions which are ranked in terms of priority. A recipient is shown whichever Proposition they meet the conditions of first.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Inbound SMS
| Mobile | Received timestamp | Received text | Flow execution id (optional) | |
|---|---|---|---|---|
| yellow@sweetmail.com | 34567890 | 17.05.2017 10:23:12 | Agilliccandy signup yellow@sweetmail.com | 40048 |
Format Explained
Recipient ID - The unique ID of the recipient who sent the inbound SMS.
Mobile - The phone number of the recipient sending the inbound SMS.
Received timestamp - The date and time Agillic received the inbound SMS.
Received text - The full text of the inbound SMS.
Pages
| Page | Page visit timestamp | |
|---|---|---|
| pink@sweetmail.com | login | 23.03.2017 11:22:07 |
Format Explained
Recipient ID - The unique ID of the recipient who visits the page.
Page - The name of the page the recipient visited.
Page visit timestamp - The date and time when the recipient visited the page.
Prints
| Flow | Step | Template | Communication Status | Communication timestamp | Error | Flow execution id (optional) | |
|---|---|---|---|---|---|---|---|
| red@sweetmail.com | Discount Campaign | Make Letter | Discount Letter | SUCCESS | 07.08.2018 10:24:20 | 80029 | |
| blue@sweetmail.com | Discount Campaign | Make Letter | Discount Letter | SUCCESS | 07.08.2018 10:24:21 | 80029 | |
| black@sweetmail.com | Missing Contact Information | Generate Print File | Missing contact information letter | ERROR | 02.07.2018 16:15:19 | Not sent because the item has not been published | 80030 |
Format Explained
Recipient ID - The unique ID of the recipient who the print file was generated for.
Flow - The name of the Flow that sent the Print File.
Step - The name of the Step which sent the Print File.
Template - The name of the Print File as it appears in the Channels module at the time of exporting. If you changed the Print Filename after exporting, you won't be able to find it in the Channels module unless you know its new name.
Communication Status - How the recipient interacted with the Print.
- SUCCESS signifies that the Print File has been successfully sent to your export destination, as defined by the Export Profile.
- ERROR signifies that the Print File wasn't correctly sent to your export destination.
Communication Timestamp - The date and time the Print file was generated.
Error - The reason why Agillic could not generate the Print file.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Push Notifications
| Flow | Step | Template | Communication Status | Communication timestamp | Error | Flow execution id (optional) | |
|---|---|---|---|---|---|---|---|
| red@sweetmail.com | Add to Wishlist | Send Push Notification | Add to Wishlist | SUCCESS | 07.08.2018 10:24:20 | 70029 | |
| blue@sweetmail.com | Add to Wishlist | Send Push Notification | Add to Wishlist | SUCCESS | 07.08.2018 10:24:21 | 70029 | |
| black@sweetmail.com | Purchase Flow | Send Push | Purchase Push Notification | ERROR | 02.07.2018 16:15:19 | Not sent because the item has not been published | 70030 |
Format Explained
Unique Recipient ID - The unique ID of the recipient who received the Push Notification.
Flow - The name of the Flow which sent the Push Notification.
Step - The name of the Step which sent the Push Notification.
Template - The name of the Push Notification as it appears in the Channels module at the time of exporting. If you changed the Push Notification name after exporting, you won't be able to find it in the Channels module unless you know its new name.
Communication Status - How the recipient interacted with the Push Notification.
- SUCCESS signifies that the message has been successfully sent to your notification service. All further processing happens outside Agillic by the notification service.
- ERROR signifies that the SMS was not correctly sent and received by the notification service.
Communication Timestamp - The date and time of the deliverance of the message to your notification service.
Error - The reason why Agillic could not process the Push Notification successfully. Contains information, if the Communication status is 'ERROR'.
Web Tracking Data
|
|
AGILLIC_ID |
PAGE |
TIME |
|---|---|---|---|
| blue@sweetmail.com | .lw- | www.Agilliccandy.com/article/Licorice-Candy | 2018.01.12 12:05:25 |
| white@sweetmail.com | .rc- | www.Agilliccandy.com/article/Caramel-Candy | 2018.01.15 16:03:20 |
| black@sweetmail.com | .dl- | www.Agilliccandy.com/article/Chocolate-Candy | 2018.01.21 20:12:17 |
Format Explained
Email - The unique ID of the recipient who visits the page.
Agillic_ID - The AGILLIC_ID of the recipient.
Page - The stored URL of the page visited.
Time - The date and time when the recipient visited the page.
|
COOKIE_ID |
PAGE |
TIME |
AGILLIC_ID |
|---|---|---|---|
| LAJPVkJHEJA8V7r_u3j41HsBLpLt | www.Agilliccandy.com/article/Licorice-Candy | 2018.01.01 08:03:13 | .pe- |
| Lqp6VEI24RyKYMlm6h-APLFlq1nP | www.Agilliccandy.com/article/Caramel-Candy | 2018.01.03 12:04:53 | |
| LjLfVpKSrjpezVS4Iw9RAFF4MQag | www.Agilliccandy.com/article/Chocolate-Candy | 2018.01.05 15:32:23 |
Example where the table includes unknown recipients
Facebook Custom Audience
|
|
Flow |
Step |
Custom Audience |
Action |
Timestamp |
Error |
Flow execution id (optional) |
|---|---|---|---|---|---|---|---|
| blue@sweetmail.com | Social Media Campaign | Add to Chocolate Facebook Campaign | Likes chocolate | Added | 2018.02.22 12:59:52 | 50065 | |
| white@sweetmail.com | Social Media Campaign | Add to Chocolate Facebook Campaign | Likes chocolate | Added | 2018.01.15 16:20:01 | 50066 | |
| black@sweetmail.com | Social Media Campaign | Add to Vanilla Facebook Campaign | Likes vanilla | Add failed |
2018.08.11 12:15:59 |
Custom audience is missing | 50067 |
Format Explained
Unique ID - The unique ID of the recipient who visits the page.
Flow - The name of the Flow.
Step - The name of the Facebook Custom Audience Step.
Custom Audience - The name of the Custom Audience in Facebook.
Action - The Status of the attempt to add or remove the recipient. Status can also be 'Waiting for confirmation', meaning that Agillic sent a request to Facebook and are awaiting for a result of execution of the request.
Timestamp - The date and time when Agillic attempted to add the recipient to the Custom Audience.
Error - Shows why the action failed. It is only filled if 'Action' is 'Error'.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Google Customer Match
|
|
Flow |
Step |
Customer List |
Action |
Timestamp |
Error |
Flow execution id (optional) |
|---|---|---|---|---|---|---|---|
| blue@sweetmail.com | Social Media Campaign | Add to Chocolate Google Campaign | Chocolate interest | Added | 2018.02.22 12:59:52 | 65014 | |
| white@sweetmail.com | Social Media Campaign | Add to Chocolate Google Campaign | Chocolate interest | Added | 2018.01.15 16:20:01 | 65015 | |
| black@sweetmail.com | Social Media Campaign | Add to Vanilla Google Campaign | Vanilla interest | Add failed | 2018.08.11 12:15:59 | Custom audience is missing | 65016 |
Format Explained
Email - The unique ID of the recipient who visits the page.
Flow - The name of the Flow.
Step - The name of the Google Customer Match Step.
Customer List - The name of the Custom List in Google Ads.
Action - The Status of the attempt to add or remove the recipient.
Timestamp - The date and time when Agillic attempted to add the recipient to the Customer List.
Error - Shows why the action failed. It is only filled if 'Action' is 'Error'.
Flow execution id - This contains the unique Execution ID, to which the execution belongs.
Comments
Can this article be improved? Please let us know, and we will update the article
0 comments
Article is closed for comments.