Explains the system behavior when an end-user unfollows on the LINE app in an environment integrated with Marketing Cloud Engagement and LINE. Provides guidance on the automatic integration mechanism when using a Webhook, how to identify the contact status by the presence or absence of a record from the GroupConnect channel data views, and the meaning of the IsActive field.
In an environment where Marketing Cloud Engagement and LINE are integrated via Webhook, follow and unfollow actions on the LINE app are automatically integrated into Marketing Cloud Engagement. This state change is reflected not by updating a specific status value, but by the presence or absence of a contact record in the GroupConnect channel.
Q. Which data views can be used to check currently registered contacts and contacts removed due to unfollowing?
A. Depending on the contact registration status, they can be checked from the following data views.
Q. Does the IsActive field included in the _MobileLineAddressContactSubscriptionView data view indicate the block status or registration status on the LINE app?
A. No. The IsActive field indicates the status of the Contact Delete feature in Marketing Cloud Engagement. It does not indicate the block status on the LINE app.
Q. In a configuration that does not use a Webhook, how is follow and unfollow information on the LINE side integrated?
A. When a Webhook is not used, integration information is not reflected in real time. To keep the information up-to-date, it is necessary to implement operations such as managing the freshness of import data and narrowing down targets before sending. To achieve automatic integration of contact information, it is generally recommended to adopt an integration configuration that uses a Webhook.
005459312

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.