Blog · 2026-09-17

Building a LINE CRM: Account Binding, Tagging and Remarketing (2026)

Turning a LINE friend list into a member database takes three layers: identity binding, tag accumulation, and segmented remarketing. This guide covers how far the official console gets you on each layer, and how to cover the rest.

Most LINE Official Accounts are stuck as a very large contact list. The friend count keeps climbing, but you do not know who any of them are, what they bought, or who is about to leave.

That is the problem a LINE CRM solves: turning anonymous friends into members with a shape. There are three layers, and they go in order.

Layer one: identity binding

This is the foundation of any LINE membership system, and it is the step most people skip.

LINE gives you a platform-side user identifier. Your own membership system has its own account numbers. Those are two completely separate numbering schemes. The same person is a random string on LINE and member A00123 in your system, with nothing connecting them.

Joining them means building a binding table, and it has to be built strictly:

Once binding is solid, tags, pushes and remarketing have something to stand on. Without it, your LINE tags are just stuck to a random string.

Layer two: how tags accumulate

Tags are the raw material for segmentation. There are five sources, and they split into two groups by whether they need development work.

The limit in the official console is clear: tags can only be applied by hand, one at a time, with no way to tag based on what a customer did. Once support volume rises you cannot keep up, incomplete tagging follows, and inaccurate segmentation follows that.

Automatic tagging is the dividing line between a LINE CRM that runs and one that does not.

The best value opening move in practice is to treat every Rich Menu cell as a tagging entry point. A tap on "Sensitive skin" tags them sensitive skin. A tap on "Book" tags them high intent. They are classifying themselves for you, and it costs nothing in message fees. Menu design is covered in the complete LINE Rich Menu guide.

Layer three: segmented remarketing

With binding and tags in place, remarketing becomes possible. And on LINE, segmentation is a cost problem first.

LINE bills broadcasts by recipient delivered. With 10,000 friends and four campaigns a month, sending to everyone is 40,000 messages at about 8,200 TWD. Segmenting down to the 3,000 relevant friends per campaign is 12,000 messages at about 2,600. That is 5,600 apart, with a lower block rate on top. The full calculation is in the complete LINE broadcast guide.

The first return on segmentation is the message spend you did not make. The conversion lift comes later.

Four common remarketing scenarios:

All four require knowing that person's state, which is why they all sit on top of layers one and two. Without binding and tags, none of them are possible.

Manage by lifecycle stage, not tags alone

Tags describe interests well: sensitive skin, likes spicy food, follows brand A. They describe progress badly. Progress needs stages.

A workable split is to put every friend into a lifecycle: newly added, engaged, registered, first purchase, active, VIP. Everyone is in exactly one stage at a time, and they only move forward.

The benefit is that you can see at a glance where people get stuck and where they drop out. If large numbers sit at newly added and never reach engaged, the problem is your welcome message and your Rich Menu. If they stall between registered and first purchase, the problem is the incentive for that first order.

Tags answer who they are. Stages answer how far they have come. You need both.

We built the whole thing into a product

Those three layers run as one system in our LINE OA platform:

• CRM contact management: user profiles, behaviour trails and the tag system in one place, so support sees what this person tapped and which stage they are at before picking up
• 8-stage funnel tracking: every friend sorted into a lifecycle stage automatically, with stalls and drop-offs visible at a glance
• Segmented push: pick recipients by stage, tag and behaviour, so message spend goes to the right people
• API integration: pull in website behaviour and order data for automatic tagging, and handle member binding
• Keyword auto-reply: keyword, event and condition triggers, tagging at the moment of interaction
• AI support agent: RAG knowledge base plus an LLM, handing off to a human when it cannot answer

Three tiers, monthly fee in USDT, no lock-in:

If a LINE CRM is what you are after, CRM contact management and API integration both sit in the Professional plan. The official account in your plan is registered under your own name, not parked under ours. Full specs are at LINE OA platform. For deeper automated workflows, see marketing automation.

FAQ

Can I run a CRM from the LINE Official Account console? Only halfway. The console has tags, but they have to be applied by hand one at a time, and there is no member binding. Automatic tagging and connecting a LINE identity to your own membership system need the Messaging API or a third-party platform with those modules.

Does a LINE membership system have to include binding? If you only want to push offers, you can send without it. But the moment points, orders or membership tiers from your own system are involved, binding is mandatory. Otherwise the bot has no idea who it is talking to.

Is there a limit on LINE tags? The number of tags in the console and the chat history retention period can both be raised through a separately priced advanced chat plan. That is an independent add-on with nothing to do with your message allowance, and the two get confused constantly.

How much does segmentation save? It depends on your friend count and how often you broadcast. With 10,000 friends and four campaigns a month, sending to everyone is about 8,200 and segmenting is about 2,600. More friends and more frequent sending means bigger savings.

Where should I start? Start with tagging from Rich Menu taps. You can set that up in the console with no development work and no message fees. Once tags have built up and you want abandoned cart and reorder reminders, deal with member binding and API integration then.

The console capabilities and billing rules in this article come from the LINE Official Account manual and the LINE Developers documentation. Specs change, so treat the current information in the official docs and the console as authoritative.