Eagle Eye process

Craig - account director
Rob - tech
Rohan - JLP integration - abinitio

click to edit

Pre Setup

Matrix initial data

Plnning (final rewards list and inital data email discussion)

Inclusions and nominations

click to edit

Two weeks

Content can also be a problem with images being updated.

Supplier funded

Timings of 6 weeks is too long for

Ammends are made to the brief whilst data is being access

Pickup Reward, stekeholders aren't able to confirmweeks aghea

If we reduced to 4 weeks we would have to say no

click to edit

Setup

EE AEM

click to edit

Matrix

click to edit

Welcome rewards, if we could apply multiple issuances dates to one welcome reward. Can only setup one issuance date - Always on version? The reason we don't have that, the end data will be some time in the future.

Newer campaign types can set the expiry date to today + 60 days

SR codes vs campaign ID for the welcome which is different each time, SF would rather have campaign ID

Can only allocate one issuance for one reward

Is a date even a requirement -might be able to not set an issuance date before).-can set coupon expiry to +60 days

Welcome reward, can we automate this setup?

AEM

click to edit

Time spent setting up

Preview is a big help, but some things don't pull through (T&C's missing), from isn't visible all in one and have to slide around the screen

AEM boxes are really small

Barcodes are now managed by JLP Loyalty team

Reporting

Maryam setup a file, two teams are involved in Abinitio to upload the file (there is a small window)
JLP upload server, that uploads at 18:30, Mat Maclan
So if the file is generated after 18:40, then it goes the next day.

Issues in the data - eg dupliates, or columns not supporting null values.
Maryam needs to have the file ready by 4pm

File gets sent to EE, EE will look for a file to process, between 18:30 and 19:30
Chance to ask for manual run

Time to process is a few hours

If files were smaller, we could think about having multiple runs per day

Hand back file from EE, that triggers SFMC

Data comes back into the database

response file picked up by 8am next day, then abinitio landing, then validations, (check number of records sent vs received), ingestion error message - process fails

Some times doesn't receive file at 8am

Affects updates in PCD

Problem with testing code, because they've been allocated, but can't perform a life test until ....
Codes created, sasha tested, can't test if it is working for an allocated number (wont know if the Teathering works)

TEst wallet, single API call to put that account into the account

We would want the wallet to receive every single offer

API or test wallet file

click to edit