The Channel Field You Should Never Leave Blank

One field carries your listing's identity to the channel. Leave it blank and the channel quietly fills it for you, and you find out a season later.

Last updated: October 14, 2026

Every listing you connect carries one field that sells nothing. It isn't the title, it isn't the photos, and a guest will probably never read it. It's the name that ties your unit to the channel's own record. Leave it empty and the channel puts something there for you. You usually find out a season later, in a report you can't read.

Key Takeaways

• The field decides which record is yours. It links your unit to the channel's own copy of it, and every statement, booking and rate change travels along that link.
• A blank field isn't empty for long. The channel substitutes a default, usually drawn from your account name or the address you registered.
• Guests rarely complain about it. The page still loads and bookings still arrive, which is why a wrong value can survive for months.
• You set it once per channel, not once per listing. Four connections mean four records, and four chances to leave one name out.
• Check it quarterly, and after every reconnect. Two minutes of reading beats a season of untangling a report that merges two units.

What the blank field actually controls

Start with what it isn't. It isn't the headline guests read on the channel. That one you publish, edit and rewrite whenever a season changes. The identity field sits behind it, and its only job is to say which of your units this record belongs to.

That single link does more work than it looks like. When a booking lands, the software has to know which unit of yours just sold. When a statement arrives, you have to know which unit it covers. When you change a rate, the change has to travel to the right record and no other. All three of those depend on the identity string matching on both sides.

So the field has an unusual failure mode. Get it wrong and nothing looks broken. The channel page renders, the photos load, the price is right, and guests keep booking. What quietly stops working is the joining, not the showing.

There's a second, slower cost. If two units end up carrying the same identity or no identity at all, their numbers arrive welded together. You don't see it in the nightly rate. You see it when you try to work out which unit earned what, and the answer comes back as one line instead of two.

Here's the concrete version. You host one apartment. It appears on four channels and once in your own records. That's five places holding a name for the same door. Four of them are copies and one is the original, and the identity field is the thread telling you which copy answers to which original. Cut the thread and the copies don't disappear. They just stop being yours.

How a filled-in default reaches guests

A channel doesn't leave a blank alone. It fills it with whatever it already has, and what it already has is rarely your wording. The usual substitutes are the name on your account, the address you registered, or the record created most recently in that account.

That produces two different kinds of wrong. The harmless-looking kind is generic: your account name appears where your unit's name should be, so every unit reads the same. The expensive kind is contamination, where a neighbouring unit's name lands on this record and stays there.

The tell shows up in the places guests do read. An automated message that names the place differently from the listing page. A confirmation that carries a name you never typed. A guest who writes back to ask whether the place named in that message is the one they booked.

What makes this so slow to catch is the split between showing and joining. Nothing on the guest-facing page depends on the identity field being right. So the value can be wrong for a whole season while every stay goes smoothly, and you only meet the problem when an export lands in front of you and the names don't line up with anything you recognize.

The fix is boring and it isn't a setting you can turn on. It's a string you type, spelled the same way every time, on both sides of the connection.

Setting it once for each channel

The order is what makes this stick. Name the unit in your own records first. Pick one spelling and one format, and don't decorate it with the season, the view or the furniture. Short strings survive better than descriptive ones, because short strings are the ones you notice going wrong.

Then write that same string onto each channel record before you connect it. Do it while you're setting the listing up, not afterwards, because afterwards you'll be reading it off a statement instead of a form.

Names that resist drift are the dull ones. "Sea View Apartment 2" gets reworded the moment the view changes or the second unit sells. "Unit 2" survives it. Pick the name a stranger could match to a door without asking you a question.

This matters more than it sounds, because a direct connection doesn't reach one place. It reaches four channels, each of which keeps its own copy of your listing: Airbnb, Booking.com, Agoda and Trip.com. Four records means four identity fields, and it only takes one left empty for a default to slip in.

Keep the string stable once it's right. Renaming a unit to match a redesign is fine on the guest-facing title and expensive on the identity field, because that's the value the two sides are matching on. If you do need to change it, change it on both sides in the same sitting.

One more habit pays off here. LOCALSBNB's calendar shows each connected channel's source rate and source status, so when four records carry similar names, you can still tell which source you're reading. It's a small piece of information, and it's the piece that stops you fixing the wrong record.

A five-minute check to run each quarter

The check itself is a list you read, not a task you perform. Open the channels you're connected to. Read the name on each record. Read the same names in your own list. Then look for two things: a name you never typed, and a unit that appears twice.

Run it on a schedule rather than when something feels off, because nothing about this field ever feels off. The quarter boundary is a good trigger. So is the week after any migration, import or handover to a co-host, since a re-created record is exactly where a name goes missing.

The failures this catches are quiet ones. A unit whose statement arrives in two halves instead of one. A guest message addressed to an account rather than to a place. A report where a single line carries the nights of two doors. None of those announce themselves, and all of them get cheap to fix once you can see the names together.

Fix what you find in the right direction. Correct the name in your own records first, then correct it on the channel, and use the calendar's source status to confirm the channel you just edited is the one still reporting. If you patch the channel alone, the next sync is entitled to overwrite it.

The last item is the one people skip. Write down the check itself somewhere you'll meet it again, with the date you ran it. A list of four names and a date takes a minute to write and tells you, next quarter, whether anything actually moved.

If you'd rather read those four connections side by side while you check them, localsbnb.com keeps the channels and their source status on one screen instead of four browser tabs.

FAQ

Is the identity field the same as my listing title?

No. The title is the line guests read on the channel. The identity field is the string that ties your unit to the channel's own record. You can rewrite the title every season and the identity field should stay exactly as you set it.

What actually happens if I leave it blank for a while?

The channel substitutes a default, usually from your account name or your registered address. The page still loads and guests still book, which is why the problem can survive for months without anyone mentioning it.

Do I have to set it again after a reconnect?

Yes. Any time a record is re-created or re-imported, read the name on both sides before you walk away. Setting the link takes two minutes. Pulling two units apart in a merged report takes a lot longer than that.

None of this needs a new tool or a bigger budget. It needs one string, spelled the same way in four places, and a habit of reading it once a quarter. If the four names have drifted apart on your account, localsbnb.com is a reasonable place to put them back side by side.

---

This is general advice for hosts, and it isn't legal, tax or insurance advice. Rules and platform terms vary by place and change over time; check the current requirements of your local authority and the current terms of each platform you use.