Profile View

Profile Navigation

APSIS One provides you with the opportunity of taking a close look at the profiles created for those who provide you their consent. This allows you to have a thorough understanding of their interest in your brand or services, as well as to better categorise and sort through different types of customers or prospects.

Not only is it possible to view and analyse profiles, but you can also perform different administrative tasks that help you stay GDPR compliant, like exporting and forgetting profiles.

Don't forget to tag! Tagging profiles you have any contact with can benefit your organisation greatly in order to communicate with them.

Click on a heading on the left side navigation to jump to any other part of this article.

Here's some basic information about what you can see in a 360° Profile view.

Click on an item below to expand:

Accessing a Profile

How to Access a Profile

1. Make sure you're in the Profiles tab on the top left side of the page.

4-Tab-profiles.jpg

 

2. Select the section you'd like to see by clicking on the drop down menu on the right side, on top of the list. You will only see the sections you've been granted access to, and no section options if you only have permission for one section.

2-drop.jpg

 

You'll see the Unknown and Known profiles gathered in a list.

2-unknown.jpg

1-known.jpg

 

3. Double-click on a profile from the list, or search for one by using the search bar. This search is, of course, section-specific.

3-search.jpg

 

You'll see something like this:

profiles1_1.png

 

4. Take a look at the left side menu. There you will see the following tabs:

Details: All the essential information about the profile.

Response Data: Statistics on how they performed with the Email campaigns they received or Marketing Automation flows they entered.

Achievements: Points and other data they earned by reaching an Achievement node in a Marketing Automation flow.

Website Interactions: Their browsing history with your website. Most viewed pages and products, and searches.

 

5. Click on one of the tabs to see the profile information that corresponds with it.

Expand another part of this drop-down to read more about a specific tab.

Profile Details

Basic Information  

The first thing you'll see is the profile owner's name and Email address.

7-name.jpg

 

They have the option to provide consent to different communication channels. To the right of the name you'll see the icons representing which channels are associated with the profile.

Review when their profile was added to your Audience and when they were last active with your website or brand (opened an Email, browsed through your website...).

 

Attributes

Have they provided their phone number for SMS consent yet? Their Mobile phone number will appear here. So will their CRM ID, which is their unique internal customer id, as long as it's been added through your API or a manual file import. Read more about Attributes...

8-lastactive.jpg

 


 

Engagement Scores

How do they engage with your brand?

9-info.jpg

 

Opened stands for the amount of times they opened your Emails.

Open rate refers to how many Emails they opened in relation to the amount they received.

16-equation.jpg

 

Click rate refers to how many Email links they clicked, in relation to the amount of Emails they opened. Unique clicks/opens is the number of links that they have clicked or emails opened, regardless of how many times. 

17-equation2.jpg

 

Revenue is the amount of money they've invested in your brand.

 


 

Consent lists & Topics

From About Profiles:

"Visitors may belong to more than one Consent list, depending on how you decided to organise your Topics. If, for example, your business has a wide range of products (anything from home appliances to products for house pets) you may create a Consent list for each and then add Topics within the lists to keep track of their preferences (kitchenware, home decor, rabbit food and premium bedclothes)."

So, since your visitor may have provided different types of consent for different Topics, their channel preferences will be listed here as well. For example, they might be interested in receiving SMS communications for women's sportswear, but in the case of sports equipment they only wish to receive Emails.

6-lists.jpg

 


 

Profile Address

If your visitor has provided their home or work address, it will show up here.

This information may come from them completing their profile information as you requested in your website, or from completing a purchase, yet as of now it fully depends on your API or a manual file import. Learn more about importing profiles...

10-address.jpg

 


 

Segmentation

Where does this profile belong in your communications? Take a look at how your visitors compare with each other and get to know the details behind each segment.

Under Segments, you can see the segments that this profile matches according to its attributes, tags, response data, website interactions, etc.

11-segments.jpg

 

Remember that segmentation feeds from multiple channels! If you have some doubts about how this works, read more about segmentation.

 


 

Profile Tags

Tags are internal markers that can be manually applied to profiles, and here's where that is done!

From About Profiles:

"Tags are internal and the relevance of a tag depends on the creator of the tag. Attributes reflect the reality of the data in the profiles, while tags don't have to. For example, if a user imports profiles with the File Import Wizard and tags them as "Special Import 19", then it will be possible to filter the recipients of an email send-out to make sure only those profiles tagged receive the email."

To add a tag to the profile, simply enter the tag and click add. Need more information? Head over to Profile Tags.

Can I make pre-defined tags?

Good question! Let's head over to Account Settings.

 


 

GDPR Options

Being GDPR compliant shouldn't be a hassle. In each profile you'll get a shortcut to your GDPR related actions.

 

1. Scroll down to the bottom of the profile, and click on the GDPR button.

gdpr2_02.jpg

 

2. Click on the option that best describes your needs:

Choose Export Data if you wish to export the data from the platform and send it to its owner.

Click Lock if the individual behind the data wishes to be removed from your Audience. Once profiles are locked in APSIS One, they can never be created again.

 

Response Data

Types of Response Data Events

These are the events that will be shown under Profile Activity. When you click a specific activity, you will see a popover with more information.

Response.jpg

 

Click on an item below to read more about what the different events are and the types of data associated with them.

  Have you read about Segmentation yet?

The purpose of gathering event data in profiles is for you to be able to communicate more efficiently with the members of your Audience, and that's where segmentation comes in.

If you would like to read more about segments and segmentation, or if need more specialised, practical, information about events, we suggest you jump to our Segmentation page.

 

Email Tool Events

Click on an item below to expand:

Sent

You've sent them an Email. Here's the type of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

Delivered

An Email you've sent has been successfully delivered. Here's the type of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

Opened

They opened an Email you've sent them. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

device: Refers to the device the event took place.

location: The IP address of where the event originated.

Click

They've clicked a link on an Email you've sent them. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

device: Refers to the device the event took place.

location: The IP address of where the event originated.

id: Refers to the id of the link in the content associated with the event.

url: Refers to the specific URL associated with the event.

title: The title of the link associated with the event.

Bounced

An Email you've sent them wasn't delivered, it bounced. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

bounceCode: The code associated with the bounceReason.

bounceReason: The occurrence, associated with the Email client or provider, that caused the Email to bounce.

Here's the bounceCode and bounceReason possible values, with all hard bounces in bold.

bounceCode    bounceReason

1004

Unknown

2000

General hard bounce

2001

Recipient email does not exist

2002

Domain name does not exist

2004

Closed email account

3001

Mailbox is full

3002

Recipient email server is currently too busy

3003

Email account is inactive

4000

General error

4003

Network error

4007

SPF authentication error

4008

DMARC authentication error

4009

DKIM authentication error

9999

Unknown

 

Unsubscribe

They've decided to unsubscribe from your communications, through the unsubscribe link in an Email you've sent. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

TopicIds: The ID for the Topics that the profile unsubscribed from.

Forward

They've forwarded an Email you've sent them to another contact. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

device: Refers to the device the event took place.

location: The IP address of where the event originated.

Report Spam

They've reported an Email you've sent them as spam. Here's the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

TopicIds: The ID for the Topics that the profile unsubscribed from.

targetId: The ID for the Consent list that is associated with the event.

 

SMS Tool Events

Click on an item below to expand:

Sent

You've sent them an SMS. Here's the type of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

Delivered

An SMS you've sent has been successfully delivered. Here's the type of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event.

Bounced

An SMS you've sent them wasn't delivered, it bounced. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

bounceReason: The occurrence, associated with the mobile number, phone carrier, etc., that caused the SMS to bounce.

Unsubscribe

They've decided to unsubscribe from your communications, through the unsubscribe link in an SMS you've sent. Here's the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

maFlowId: The name of the tool that initiated the activity.

Topic: The ID for the Topic that is correlated with the event.

 

Marketing Automation Tool Events

Click an item below to expand: 

Enter Flow

The profile entered a Marketing Automation flow. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the profile moved onto. In this case, the ID corresponds with the node that follows the Listen Node in this particular flow.

Move Profile

The profile moved, in a Marketing Automation flow, from one node to another. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

srcNodeId: Refers to the ID of the source node, or the ID of the specific node that the profile moved from.

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the profile moved onto.

Exit Flow

The profile left the Marketing Automation flow. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

points: The abstract numeric value assigned to the profile upon reaching the Finish node and completing the flow.

reason: The reason that the profile left the flow:

  • Finished: The profile reached the Finish Node and completed the flow.
  • Match tags: The profile matched the tag specified in the Flow Settings under Terminate.
  • Over limit: The profile has entered the flow the maximum amount of times specified in the Flow Settings.
  • Missing consent: The profile has withdrawn their consent. Either they opted out or they have been deleted from Audience.
  • Reset: The profile was removed from the flow when pausing and reactivating the flow.

srcNodeId: The ID of the specific node that the profile left the flow on.

Third Party Events

Whenever an email is sent through the Marketing Automation tool, the events are then part of the Email tool domain. Check the Email tool events for more information.

 

Achievements

Profile Achievements

When a profile earns an achievement set by an Achievement Node in a Marketing Automation flow, the achievement, points and monetary value will be displayed here.

Achiev.jpg

 

Here are the types of data associated with this event:

achievementId: A unique ID for the achievement associated with the Achievement Node.

type: What type of achievement the profile earned: MQL, SQL or PQL. The type of achievement is a part of the Achievement Node settings.

points: The abstract numeric value assigned to the profile upon reaching the Finish node and completing the flow.

value: The numeric monetary value assigned to the profile upon reaching the Finish node and completing the flow.

sourceType: The tool considered as the source for this event. In this case, it's the Marketing Automation tool (For now this is the only source creating achievements, but we'll let you know when other tools start doing it too).

sourceId: The ID for the specific activity that corresponds with the achievement.

Ecommerce

Ecommerce Events

Ecommerce events are a part of the Expand Ecom package for APSIS One. Read more about Expand Ecom...

Click on an item below to read more about what the different events are and the types of data associated with them.

Cart abandoned

The Profile added one or more items to their cart on your website and then became inactive for at least 60 minutes.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId
  • currency
  • totalValue
  • url

 

Product viewed

The Profile viewed or opened a page for one of the products in your website.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId
  • sku
  • name
  • group
  • category
  • size
  • thumbnail
  • unitPrice
  • currency
  • stock

 

Browse abandonment

The Profile browsed your website and became inactive for at least 60 minutes.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId

 

Product purchased

The Profile completed a purchase in your website for one or more products. This event is logged per product purchased; if their cart contained multiple products, the event will be logged once per every product.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId
  • orderId
  • sku
  • name
  • group
  • category
  • size
  • thumbnail
  • unitPrice
  • currency
  • stock
  • quantity
  • totalValue

 

Product carted

The Profile added an item to their shopping cart in your website. This event is logged per product carted; if they add multiple products to their cart, the event will be logged once per every product.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId
  • sku
  • name
  • group
  • category
  • size
  • thumbnail
  • unitPrice
  • currency
  • stock
  • quantity
  • totalValue

 

Cart purchased

The Profile completed a purchase in your website. This event is logged once per cart. For an event that describes the products in the cart, see Product purchased event.

Here are the types of data associated with this event:

  • websiteId
  • sessionId
  • cartId
  • orderId
  • currency
  • totalValue

 

Website Interactions

Types of Website Interaction Data Events

These are the events that will be shown under Website Interactions. When you click a specific interaction, you will see a tooltip with more information.

WebsiteInt.jpg

 

Click on an item below to read more about what the different events are and the types of data associated with them.

  Have you read about Segmentation yet?

The purpose of gathering event data in profiles is for you to be able to communicate more efficiently with the members of your Audience, and that's where segmentation comes in.

If you would like to read more about segments and segmentation, or if need more specialised, practical, information about events, we suggest you jump to our Segmentation page.

 

Sign-Up Bar Interactions

Click on an item below to expand:

View

They navigated into a page where you placed a sign-up bar. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

Submit

They submitted their Email address to you via your sign-up bar. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

Email: The Email the person associated with the profile provided with their explicit consent.

Return Offer Click

They clicked on the CTA/button link on your sign-up bar. Here's the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

offer-url: Refers to the URL associated with the Return Message CTA of the Sign-up bar they clicked.

 

Cookie Banner Interactions

Click on an item below to expand:

View

They navigated into a page where you placed a cookie banner. here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

Submit

They submitted their cookie consent via your cookie banner. Here's the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

 

Auto Collect Data

Click on an item below to expand:

  Did you set up Auto-Collect?

This type of events will only be displayed if you have created an Auto-Collect activity. This activity allows you to track data from integrations with Facebook ads, Google Analytics, Google SEO/SEM, and many more.

Read more about Auto-Collect...

Google Analytics

These interactions are fed into APSIS One if you use UTM parameters to track interactions with Google Analytics. If the APSIS One Tracking Script identifies a page load with any of the supported UTM parameters, it will enrich the Profile with a Google Analytics event. For example: http://www.example.com/?utm_source=exampleblog&utm_medium=referral&utm_campaign=summer-sale

Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

utmcampaign: Corresponds with a Google Analytics parameter. This one refers to the text used to identify a particular campaign.

utmcontent: Corresponds with a Google Analytics parameter. Useful to differentiate similar content or links within the same Email.

utmmedium: Corresponds with a Google Analytics parameter. Refers to the communication medium used to display the content, like whether it's an Email newsletter, a banner, etc.

utmsource: Corresponds with a Google Analytics parameter. Identifies the origin on the website interaction, if it was visited by clicking on a website, via a Google search, etc.

utmterm: Corresponds with a Google Analytics parameter. In the case of the campaigns being tagged with certain keywords, this parameter allows you to specify the keyword.

Google SEO/SEM

These interactions are fed into APSIS One if you have a Google SEO/SEM integration. If the APSIS One Tracking Script identifies that a visitor has arrived to the website from a google domain. They can be from a paid source, identified with a Google Click ID (GCLID) parameter in the URL, or an organic source.

Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

type: Corresponds with Google SEO/SEM. Determines whether the traffic comes from a paid (GCLID parameter in the URL) or an organic source.

Page view

They viewed or browsed a page in your website. Note that all this data is fed to APSIS One as it is mapped in your website's code. Here are types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

title: The name of the product viewed by the profile upon browsing your website.

category: The product category that was viewed by the profile upon browsing your website.

price: The price of a product that was viewed by the profile upon browsing your website.

image: The image URL of a product that was viewed by the profile upon browsing your website.

There is, of course, user-defined data. If you chose to collect any specific data and added it as a custom field, it will appear here.

File download

They downloaded a file from your website. This is detected when the link contains a file extension (like .PDF, .EPUB, .ZIP...) or a "download" parameter. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

link: A link to the file that was downloaded.

title: Title of the file's link.

Site search

They performed a search in your website. This event is picked up by the URL's search key, which you entered in your Auto-Collect activity. Read more about data sources...

Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

term: The search term used by the profile.

Facebook Ad Referral

They reached your website from a Facebook ad, with a Facebook Click ID (FBCLID) parameter that is automatically added by Facebook when linking to your website. For example: http://www.site.com?fbclid=juihd8239732buibiee32809jeee2i90. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

term: The search term used by the profile.

type: (Coming soon...)

 

Product Views

Click on an item below to expand:

Product Views Data

They viewed a product page upon browsing your website. This will only appear if you have completed the Website activity Product Views in Collect. Here are the types of data associated with this event:

activityId: The ID for the particular activity that is considered the source of the event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The website where the website traffic originated, or where the profiles were before reaching the domain associated with the event.

url: Refers to the specific URL associated with the event.

domain: The domain where the event took place.

 

Cart Events

Click on an item below to expand:

Created

Coming soon...

Product

Coming soon...

 

Order Events

Click on an item below to expand:

Created

Coming soon...

Product

Coming soon...

 

Conversion Events

Click on an item below to expand:

Basic

Coming soon...

 

 


 

Profile Tags

Tags are internal markers that can be manually applied to profiles. They can be created from your account settings.

To read more about how to create tags from your account settings, go to this article. Only Admin Users may access the account settings.

These are the main differences between attributes and tags:

- Tags, themselves, do not contain data. Attributes can be understood as being something like "type of data = data" (gender = female) while tags are more like "Label = yes / no" (either tag is applied or it isn't).

- Profile tags are applied manually. Attributes, on the contrary, gather the data automatically and feed it into the profile. In order for a profile to have a tag, a user must apply the tag. Alternatively, if a file containing profile data is uploaded, they can be tagged in advance.

- Tags are internal and the relevance of a tag depends on its creator. Attributes reflect the reality of the data in the profiles, while tags don't have to. For example, if a user imports profiles with the File Import Wizard and tags them as "Special Import 19", then it will be possible to filter the recipients of an email send-out to make sure only those profiles tagged receive the email.

 


 

GDPR Options

Individuals always have the option to unsubscribe or opt-out from your communications, they also have the right to request that you share their data with them as well as that you erase it.

This part of the profile view allows you to export or lock profiles.

Profiles28_02.jpg

 

Click on an item below to expand:

Exporting Profile Data

How to Export Profile Data

1. Locate and open the profile you would like to export data from.

prof3_01.jpg

 

2. Scroll down until you see the GDPR button.

gdpr2_02.jpg

 

3. Click Export data.

Profiles28_02.jpg

 

4. A file download will begin. The data will be exported in JSON format.

 

Locking Profile Data

How to Delete Profile Data

This option will allow you to manually lock data from a single profile.

1. Locate and open the profile you would like to lock.

ProfileView.jpg

 

2. Scroll down until you see the GDPR button.

gdpr2_02.jpg

 

3. Click Lock Profile.

Profiles28_02.jpg

 

4. You will see a popup. Are you sure you would like to lock this profile?

Deleting a profile is permanent. Moreover, if the same person with the same email or phone number attempts to opt-in again, APSIS One will block the attempt and they will not be able to opt-in again to your communications. You will not be able to import the profile with the same email address or phone number either.

If yes, click Confirm. Otherwise, Cancel.

 

 


 

 

Was this article helpful?