The automation only works for simple “City, State” locations. If your primary location field in Emma includes anything in addition to “City, State” it will not work. We will need to wait to hook it up once the new version comes out. Please let Emily know if you have an account that needs hooked up but will need to wait for the next phase.
IF YOUR ACCOUNT HAS MULTIPLE ESP#’S:
Please hook up both the current ESP# and then follow the steps again to hook up any alternate ESP#’s. Please make sure that you alert Emily and make a note in Appflow.
TO HOOK UP AN APP & EMAIL PROGRAM TO THE AUTOMATION:
Go to http://dev07.clipperwebdev.com/ and enter the fields below (please copy/paste your entries from Emma so they are exact)
- Add Business Name
- Add Emma Account # (found under the Emma account settings)
- Add ESP#
- Click “Update”
- You will receive a pop up box asking you to confirm entry, click OK
- You will receive another pop up box confirming entry, click OK
CREATE A GROUP/SEGMENT IN EMMA:
- Go to Groups and make sure there is a “TLS App” group setup (if not, create one)
- Go to Audience and create a Segment
- Name: QORE Automation – TLS App
- Group – in – TLS App
- Contact Since – is after – yesterday’s date
IF YOU ADDED ONE BY MISTAKE: Please email Emily to have it removed. (don’t panic though – it shouldn’t hurt anything)
CONFIRMING SUCCESS: Check the drunk tank email that comes to Customer Service for any errors. Work with Emily to correct if/when they occur. The automation is pulling the content from the Primary Location Contact Field in Emma AND the Location within CMS (Not the “name” of the location, or even the “City” and “State” field within the Location module in CMS – but it is actually pulling from the list of locations in CMS under the Location module that you see when you click on “Add Location”, which is actually pulling from the DTO Admin) and they need to match EXACTLY (down to the spacing). We do not want to change things in CMS or the DTO Admin if we don’t have to (for many reasons) so we always want to update Emma if/when we can, however there will be instances where the DTO Admin will need updated. Chuck is the only one who can do this. Please do not update Emma or ask Chuck to update the DTO Admin without running it by Emily first. We want to make sure we are updating these in the best way and in the correct way.
EXAMPLES OF FIX OPTIONS:
INCORRECT PRIMARY LOCATION CONTACT FIELD IN EMMA:
It is listed as “Lancaster, PA” in CMS, but it’s listed as “Lancaster – PA” in Emma. Since CMS is correct, and Emma is not, you will need to update the contact field in Emma to “Lancaster, PA”, export your entire audience, remove everything from the excel file other than email address, insert a primary location column with the new updated location “Lancaster, PA” and re-import. You will need to choose “Update their records with information from this import (add and update)“ when you are re-importing, use “Update” as your source, and “Qr Automation Update” as your group.
NO PRIMARY LOCATION CONTACT FIELD IN EMMA:
If you do not have a Primary Location field at all, you will need to add one. It is a Drop Down option.
SPACE AFTER CITY NAME IN THE CMS LOCATION MODULE:
If you click on the city field in CMS under the Locations module and there is a space after the city name, it will fail. Since this information is actually pulling from the DTO Admin, we will need to ask Chuck to update it.