Eagle Eye Integration

Integrating Odicci with Eagle Eye allows you to create seamless experiences by combining Odicci's interactive content creation platform with Eagle Eye's customer loyalty and digital marketing solutions. This document outlines the steps required to integrate Odicci with Eagle Eye.

Prerequisites

  • Access to both Odicci and Eagle Eye accounts
  • API credentials for Eagle Eye

Step 1: Set Up API Access

Eagle Eye

  1. Obtain API Credentials:

    • Generate or locate your API key and secret.

      Configure API Settings:

    • Ensure that your API key has the necessary permissions for the operations you plan to perform.

Integrating your EE API to Odicci

  1. Click on your profile on the top right of the screen.

  1. Click Settings. Then Click Integrations.
  2. Scroll to Eagle Eye and click Connect.

  1. Connect your Eagle Eye.
    • Enter your Client ID from Eagle Eye.
    • Enter your Client Secret key.

Step 2: Create Interactive Content in Odicci

  1. Design Your Interactive Campaign:
    • Log in to your Odicci account.
    • Create a new interactive experience using Odicci’s design tools.

    • Configure the experience elements (e.g., quizzes, surveys, games) as per your requirements.

      Set Up Identification:

      When setting up identification of App users we are using hidden values in the studio. To connect to Eagle Eye we setup hidden fields for accountId and walletId. You can find these hidden value component in the components tab placed on the right of the screen. Hidden values will negate the need to add fields to your experience thanks to the pre-filled frame feature, you can generate your pre-filled frame link by going to the following below.


    • Ensure that your interactive experience is set to capture the data, walletIds and accountIds with the use of Hidden Fields.
    • Configure the data capture fields to align with the data structure required by Eagle Eye.

  1. Pre-Filled URL

    A pre-filled URL has to be added behind a CTA within the app in order to access the Odicci experience and push the users accountId & walletId to Odicci at the same time.

    This URL can be found on the left handside on the first frame in the studio.


  1. Map Incoming Data:

When in the Odicci studio you can find the configure screen from the wheel (⚙️) on the top right of the studio, this pop-up below will show. Enter the second tab of the configure screen, if your Eagle Eye is not enabled you would not see the screen below - make sure to connect your Eagle Eye account to activate this screen. Make sure the data fields are connected to the correct Eagle Eye fields in order to ensure you are connected to the promotion platform.

  • Map the incoming data fields from Odicci to the corresponding fields in Eagle Eye.
  • Ensure that the data is stored correctly and can be utilised for your marketing campaigns or loyalty programmes.

Step 3: Automate Processes

  1. Create Automation Rules:
  • If Eagle Eye supports automation, set up rules to automate actions based on the data received from Odicci.
  • Examples include updating loyalty points, or triggering specific marketing campaigns.
  1. Test Automation:
    • Test the automation rules to ensure that they work as expected.
    • Verify that the correct actions are triggered based on the data received from Odicci.

Step 4: Monitor and Optimise

  1. Monitor Data Flow:
  • Regularly check the data flow between Odicci and Eagle Eye to ensure that there are no disruptions.
  • Use logging and error-handling mechanisms to identify and resolve any issues promptly.
  1. Optimise Experiences:
  • Analyse the data received from Odicci in Eagle Eye to optimise your marketing experiences.
  • Use insights gained from the data to improve customer engagement and loyalty.

Conclusion

By following these steps, you can integrate Odicci with Eagle Eye to create a powerful combination of interactive content and customer loyalty solutions. Ensure to test the integration thoroughly and monitor the data flow to maintain a seamless experience for your customers.

Feel free to customise the integration based on your specific needs and leverage the full capabilities of both platforms to enhance your marketing efforts.

Additional Steps

Prize Configuration

Below is a short checklist and description of what each element of the prize page does and how to configure it.

Prize name - If the reward is a Cashpot then ensure the name is a numeric value that represents pounds in pence. Example: for a prize worth £1 call the prize “100“.

Check Reward Type - When integrated with Eagle eye the two types of rewards are Cashpot and Coupon. Cashpots have naming standards, if you are unsure of the standards then check our advanced guide below. Coupon do not have any naming standards but require an Eagle Eye CampaignID, contact a memeber of Eagle Eye to confirm your ID

Reward Type Naming Rewards EE campaignId Description
Cashpot “10”, “100”, “1000”, “10000”, “555” N/a The name of a Cashpot is IMPORTANT, the name represents a pence value, meaning if you wish to provide £1 as a Cashpot reward then you need to name the reward “100”
Coupon “Chocolate Pouches £1.00 off” *Required* Coupon names are not sensitive and can follow any convention, when applying coupons, its important to know your EE campaignId

Unlimited Prizes - There must be at least 1 Unlimited Prize on your experience, this is to ensure that once all prizes are complete users are able to obtain an outcome and not be presented a null result.

Image - Images must be well optimised and not resource intensive, in the majority of cases, they must follow a 1:1 ratio, otherwise please be cautious when using other aspect ratios for images. Contact a member of the Customer Success team if you are encountering issues with spacing and sizing.

Quantity - Can be limited or unlimited, numbers must be predefined by ASDA Rewards team and need to be checked before launch of an experience to ensure the right settings are placed.

Prize Chances - Prize chances are only configurable in the the main prize tab screen. It’s imperative that chances are set correctly before launch, this must be checked and tested internally to get the desired outcome for each prize. By default the chance dropdown menu is limited to 100, however you are able to configure your chances to whatever number you want by double clicking the dropdown.

Make sure unpublished
Double click
Change Value

Stop Pause frame

We encourage you to check if your stop pause frame is designed and branded to your companies design principles, its important for the user to feel the full cohesive experience.

The stop pause frame will come up under certain scenarios:

  • If user drops connection from experience.
  • If experience is offline.
  • If experience is undergoing maintenance.
  • If experience has an error.

Quality Assurance

To test an experience you need to do the full journey to understand if an experience is working or not, for a transaction/POS experience we need to test this customer journey from start to finish:

QA Checklist

This checklist is made to follow this customer journey and find potential failure points at each stage.

Create a transactionId for every test accountId and walletId (Eagle Eye/Apadmi) (i)
A vast array of dummy accounts and transactions (Eagle Eye/Apadmi) (ii)
Add Ids to publish URL ?accountId=123456&walletId=12345678
Run through the published URL with the Ids to see outcome (iii)
if there are errors check prize page and check set up of all prizes (v)
if there are errors check CRM integration page to see if data is correctly assigned
if there are errors check Eagle Eye integration clientID and client secret
if there are errors contact product team (Odicci)
If there are no errors, check reporting under entries to see if integration pushed.
Run through sentry logs and troubleshoot according to error message
if not resolved reach out to product team (Odicci)
If integration push was successful then integration checks are complete 👍


Possible errors:

(i) There needs to be a value entered so thats it is recognised in POS

(ii) Must use test accountId and walletId’s that are not currently in use or EE will throw wallet transaction already exists with reference error

(iii) EE will throw error if no valid accountId and walletId

(v) If naming conventions are not set appropriately then an error may pop up here

👍 Your experience has shown its full flow and data is pushed to EagleEye