When you have one or more ad accounts configured on the platform, you can start setting up the acquisition forms.
The forms listed in the second selection relate to the ad account you have chosen in the selection above.
Import options
The box Import contacts into a static audience, if checked, allows you to specify the name of a static audience into which the imported contacts will be placed. If the audience does not exist, it is created.
The second box, Force reactivation of unsubscribed and suspended contacts, if checked, sets to "Subscribed" the contacts that were previously in a suspended or unsubscribed status.
Reactivate only the contacts for which you have consent. Use the reactivation box with caution.
In the edit of an existing form, there is a box that allows you to enable or disable global import for all contacts belonging to the form. When creating a new form, you will find import disabled, allowing you to configure the field associations before the first import occurs.
To save the configuration for a new form, you must accept the terms in the Warranty and indemnity section. To refuse these terms in the future, after accepting them, you will need to delete the configured form (and consequently, the import of contacts from that form will stop).
After configuring the acquisition form, the page reloads to present you with additional options since the form is not yet ready to import contacts. You still need to configure the field associations between LinkedIn and the destination database.
Field associations
This table allows you to define the associations between a response to a question on the LinkedIn form and a contact field in your destination database. You can freely add and remove associations, but the primary key field in your database must always be associated with a LinkedIn question, otherwise it will not be possible to uniquely identify the contact to associate with the submission.
"LinkedIn Field" is the name of the question as visible from LinkedIn, "Database Field" is the name of the contact field within the destination database.
You can associate a LinkedIn field with multiple database fields, but you cannot associate a database field with multiple LinkedIn questions (the LinkedIn values would be overwritten).
To add a new association, use the Add association button. A dialog window will appear:
In the first selection, choose the LinkedIn form question, in the second selection choose the destination contact field. To create a new field, select Create a new field, which allows you to specify the name and identifier of the field to be created upon saving.
The system attempts to match the data type from LinkedIn to the destination database field. For example: a text response associated with a numeric field in the database may be converted to a number if the string conforms to the decimal format.
Any conversion errors may cause the contact not to be imported. A statistic is available for each form and indicates how many import errors have occurred over time.
Automatically created fields are preconfigured with the prefix LinkedIn - in the name and LI_ in the identifier.
Transcoding
If the destination field is of type list of values, an additional button appears that allows you to add a "transcoding" to convert the response options present on LinkedIn into values for the database field. For example: the gender field may have the values male / female in the form that contacts fill out on LinkedIn, but in the database field, it must be converted to M / F.
One possible transcoding case is with a text field in the database. For each option of the LinkedIn question, you can define a different text to be inserted into the database field.
A second case is with a list of values field in the database. The platform presents you with the list of possible LinkedIn responses to associate with the corresponding option of the database field.
Field associations with fixed value or expressions
Sometimes it can be useful to add the automatic value assignment for fields that are the same for all contacts, like assigning a specific value to the system field Source, for example setting a meaningful value like "LinkedIn" so that you can subsequently filter the contacts in the database that come from LinkedIn forms.
It is also possible to assign an expression to a field, such as when contacting the user which could be set as today + 2 days.