Database name

When the default database has been created, you can rename the database in Copernica.

Adding database fields

You can add fields and areas of interest through the Copernica interface. Because Spotler Connect does not fill these fields by default, it's essential to make sure they are not required to fill for profile creation. Otherwise, profiles might not be created through Spotler Connect anymore.

Name of field

When you add a field, it's best practice to use a custom name with a prefix or suffix specific to your account (for example, 'Custom_Fieldname' instead of just 'Fieldname'). Spotler Connect periodically updates the default database with new fields, and when field names overlap, Spotler Connect will overwrite the data. By adding custom pre- or suffixes, the chance of collision is minimised.

Removing database fields

You can remove existing fields from our current database, but please remember that some fields are used to propagate data back to Spotler Connect, such as the opt-in fields. When fields are removed, data for these fields through Spotler Connect will not be saved in the database anymore. If you re-create a field with the same name, data will be saved again from that moment onwards. Please note that there is no possibility to fill fields retroactively.

Changing database fields

When changing properties from existing database fields, you need to consider whether the change modifies the input that the field expects.

Changing field type

The type of field in Copernica determines the kind of input that can be processed. We do not recommend changing fields that can process any input (text or long text fields) to fields that can process limited input (number or multiple choice fields). When Copernica cannot process data from Spotler Connect, Copernica will not save the data to the profile and the field will remain empty. You will not receive an error notification when this happens, as Spotler Connect doesn't receive error notifications for this event. We recommend only changing limited input fields to text fields so that no data will be lost.

Changing field options

When your remove field options from the default database, like the 'Other' option from the field where gender is saved, this will not prevent Spotler Connect from propagating that value to Copernica. Spotler Connect normalises imported data from other channels to one of the values specified in our data model. As specified above, any data that cannot be processed will not be saved in Copernica. So make sure that Spotler Connect does not receive any input from data sources that is normalised to the option you removed from your default database.

When you add field options to Copernica, you will need to make sure that this option is added to the mappings in your Spotler Connect account. If no mapping is added, Spotler Connect will not include the new field option in the propagated data because it's not your account's options.

Changing field name

Spotler Connect can only match fields on the field name. Therefore we do not recommend changing field names in our default database, as this can lead to data loss. You can work around this issue by using database follow-ups to fill a custom field while hiding the original field from your database overviews.