Page MenuHomePhabricator

Update Remind Me Later (RML) form to post to CiviCRM and send that data to Acoustic
Open, Needs TriagePublic

Description

Currently, all fundraising banners incorporate a form the user can enter their email address into to receive a reminder to donate via email. Here is an example desktop banner. If you select the "Maybe later" link in that banner, you will see for the form I am referencing.

This form has always posted directly to Acoustic (aka Silverpop) in order to quickly get the signup in and allow the email address to be added to a program to send the reminder email. But there are some drawbacks to this approach, mainly on the reporting side. The crux of the issue here is that we’re trying to extract transactional signup data from an aggregate location (Acoustic’s main database). CiviCRM seems like a better location to store this information in a transactional manner so we can always report on the number of signups for a given banner.

Most of the fields currently submitted in the form will need to be stored in CiviCRM. Here is a list:

rml_source
rml_group
rml_country
rml_language
rml_submitDate
rml_segment
Email

These signups and their associated data will also need to be sent to Acoustic. What is the expected turnaround time for when someone submits the RML form to CiviCRM and that data being represented in Acoustic?

Related Objects

Event Timeline

TLDR: This has big security implications and needs planning, design and discussing before we could even talk about putting this on a roadmap. It may not be possible at all. However the data you are looking for may already be available with the current setup.

We have civi locked down under very tight security. The only time we have ever had a feature or form like this is the email preference center and that took a lot of effort to set up. Exposing a form to everyone who sees a banner carries more risk. Also we are pretty much booked up for any sizable feature like this until Q3, Q4 or the next fiscal (22/23). I'm going to note that this should be a requirement for the CN replacement as well.

However if your only requirements are these data points, we already capture some of these. We're currently discussing some workflow issues regarding language here: T282912. I'm going to comment on individual data points below

Could you give more info on these? How do they relate to a casual reader who interacts with a banner?
rml_source
rml_group
rml_segment

We have these in civi. They are being captured from acoustic.
rml_country
rml_language

you can derive this date by looking at the creation date in civi and subtracting one day.
rml_submitDate

I assume this is email address? You definitely already get this :)
Email

@DStrine I found an old task T195260 which was also partly about posting RML data to our servers. Should this be merged with that one? It's restricted visibility so I'm not sure if Trilogy will be able to see once merged