Interaction Round-Trip

Because your institution can both import interactions and write interactions in EverTrue, we've developed a round-trip process to help ensure data is synced daily. Interaction Round-Trip simply means that your institution can take an interaction written in EverTrue, load it back into your database, and then send those same interactions back to EverTrue in the next interaction CSV import. This process is especially important for keeping everything up-to-date when an EverTrue interaction can be edited in your institution's database. If your institution has chosen not to allow EverTrue interactions to be edited in your database, jump down to Option 2. 

Interaction Round-Trip Steps

  1. Setup an interactions import from your institution's database of record to EverTrue. 
    1. At first, this will just be a historical import of interactions. 
    2. Eventually, you'll need to add the "EverTrue Interaction ID" field to this file to complete the round-trip process. (See Steps 4 & 5)
    3. When creating the dynamic query used for this file, we recommend focusing on pulling just the deltas, which would include any EverTrue interactions that may have been edited in your database once the round-trip process has begun.
  2. Make sure you are happy with your interaction entry form and that the ability to write an interaction is enabled on both web & mobile.
    1. The interactions form will be configured with your implementation specialist, but you can always contact Support for any requested changes. 
    2. The interaction form directly impacts the CSV export format that EverTrue generates for your institution on a daily basis. 
  3. Schedule your interaction exports to be delivered daily to your EverTrue SFTP directory.
    1. EverTrue will drop of a daily file (at the time you indicate) into an /exports folder in your SFTP directory.  
    2. You'll need SFTP credentials and access to that directory to set up the full automation process (scripting the CSV file to be picked up and put back into your database).  
  4. When loading EverTrue interactions into your database, you'll need a place to import and save the EverTrue Interaction ID. 
    1. This ID will keep EverTrue from duplicating interactions when they make the full round-trip.
    2. Only interactions edited or created in EverTrue will have an EverTrue interaction ID.
    3. The EverTrue Interaction ID is only available via the generated CSV interaction export file. 
  5. Add the EverTrue Interaction ID to your interaction import CSV file for EverTrue. Contact EverTrue support if you do not have the ability to map & import the "EverTrue ID" for interactions. 
  6. You have now completed the interaction round-trip process! Keep the flow going to have interaction circulate from EverTrue to your database, and back again!

Example Round-Trip Process

Say Gift Officer George writes an interaction in EverTrue. When exported from EverTrue, this interaction is marked with an EverTrue Interaction ID of 123. This interaction is then loaded into your database and given the ID ABC. After it is loaded into your database, George is sorting through some data and realizes he needs to add more information to that interaction. Because he is already in the database, he makes the change directly there. Because this interaction has been edited in your database, that change needs to then make it back to EverTrue. This interaction should then be pulled into your next file to deliver to EverTrue for upload with both the database ID and the EverTrue Interaction ID. During ingestion, mapping the EverTrue ID ensures that we recognize the interaction and update it accordingly. Now the interaction is up-to-date in both places. 

Additional Notes

  • Interactions written in EverTrue can only be edited in EverTrue by the author or solicitor. 
  • Imported interactions in EverTrue can only be edited by the solicitor.

Option 2

It is also possible to run a single trip of data from EverTrue to your database without returning the interactions to EverTrue again. This would require you to prohibit edits in your database of any interaction imported from EverTrue. This will ensure that your database has a read-only version of the EverTrue interactions and therefore do not need to make the round-trip back into EverTrue. With this option, you are running a single stream of data to EverTrue (interactions written in your database) and a single stream of data to your database (interactions written or updated in EverTrue).  

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.