GetPaidX docs

The end-user manual for public and signed-in product features.

Search docs

Keyword search across docs titles, summaries, headings, and curated keywords.

Places and Check-InsUpdated 2026-03-07

Place Post Entry and Active Check-In Counts

How the place page invites users to create a post, what the Active check-ins count means, and how that card reflects current venue activity instead of all historical traffic.

Place Post Entry and Active Check-In Counts

Where you see this in the app

This page documents the place-page entry card that says Create a post for this place.

It sits alongside place activity surfaces and gives users a fast way to create venue-linked content without searching for the place again in the composer.

Create a post for this place

The Create a post for this place card is a venue-first authoring shortcut.

From an end-user perspective, it means:

  • start a new post already tied to this place,
  • publish something relevant to the venue,
  • help followers or members know what is happening here.

This is not just a generic create-post button dropped into the place page. It is meant to preserve place context from the start.

What Active check-ins counts

The place entry card also shows an Active check-ins count.

The key meaning is narrow: it counts hosts who are currently checked in within the active time window, not everyone who has ever posted about the venue.

That is why the UI explains that it Counts hosts checked in within the past 4 hours.

Users should read this as a live-presence signal, not as a permanent popularity metric.

How it relates to live presence

The place page groups several ideas together:

  • active check-ins,
  • live chat,
  • current people at the venue,
  • venue-linked posts.

The Active check-ins count is the quick summary of who is currently on-site or recently on-site enough to matter to those live surfaces.

What users should expect

When users create a post from this card, they should expect the place context to carry into the post flow.

They should not expect:

  • a generic blank composer with no venue context,
  • the active-check-in count to rise forever from every old post,
  • the number to represent all-time venue engagement.

Related docs

    Place Post Entry and Active Check-In Counts | GetPaidX docs | LastRevision.pro