Aptify

To read data from Aptify, PropFuel leverages the Aptify Services API, which allows us to retrieve entity information using Aptify views.

To connect with your Aptify instance, PropFuel uses the Aptify Services API. In order to support this connection, you will need to create a user account and credentials specific to the integration. More information on authentication can be found in Aptify’s documentation, we typically use Domain or SQL user authentication.

To get and sync individual person data from Aptify, PropFuel leverages two Data Objects that you will create in Aptify.

The first data object will retrieve the information for a person record. At minimum, we will need their name and email address, but we can pull other information as well. This information is stored in PropFuel to allow personalization as well as list building and filtering of response data. This varies by client, but will generally include:

• Job information (Employer, title)

• Membership information (Member type, join date, expiration date)

• Other relevant certifications or categories

This call should also include a flag or fields containing opt-out information if they have unsubscribed from all communications and should not be emailed via PropFuel.

The Get Person method should accept either a single Person ID or collection of Person IDs as a
parameter to determine what data to pass back.

This data object will be used to keep person data that is updated in Aptify in sync with your PropFuel database. It should accept a date time as a parameter, and return a list of Person IDs that have been updated since that time. We will take the list of updated IDs and run them through the Get Person data object to keep the information stored in PropFuel up to date.

In addition to pulling data from Aptify to PropFuel, you can also write response data directly to Aptify when a contact answers one of your questions. In order to do this, you will need to create an Entity in Aptify that will be used as a holding table for your PropFuel data.

This entity can be called anything you like, and it should contain the following columns

• PersonID (Used to tie the response to the person who is submitting it)

• AnswerDate (We will populate this with the timestamp of their answer)

• FieldKey (This will be entered into the PropFuel UI and writing back to distinguish what data the answer corresponds to)

• Value (This will be the answer given to the question)

You can also create additional columns to store other metadata if useful, such as the Campaign ID of the question response.

Once you have created the Entity, let us know the name and the list of columns you would like us to populate, and we will configure the writeback action in PropFuel.

Once we have the authentication information and names of the completed data objects, the PropFuel team will enable the integration for your account. This can be done within one week turnaround time, assuming the previous setup work has been completed correctly.

Once the integration is configured, you can begin using the integration by setting up views in Aptify and tying them to PropFuel campaigns.

In order to pull contacts and their relevant information out of Aptify and into PropFuel, we utilize the Views functionality of the Aptify services API. You will create more Person Views in Aptify that represent the list of people to interact with for a campaign. Once a view is created, it can be tied into PropFuel workflows to add or remove the people who show up in that view from a PropFuel campaign.

These views do not need to contain any specific demographic information as columns, only the Person ID. We will use the Person ID to match the contacts that we have previously created via the data sync we are continuously running.