Podium makes your data available through an FTP (File Transfer Protocol). Below you can view the available tables and included fields accessible for a Podium Organization. An Account Owner will need to make the request before access to the Podium FTP will be granted.
Need help accessing or building custom reports for your Podium data? Contact a Podium Expert for guidance.
Available Data Tables
Table: Feedback
Data Definitions
feedback_interaction_id: unique identifier for individual survey interaction with a customer. Similar to a review invite for surveys.
feedback_interaction_uid: unique identifier for individual survey interaction with a customer. Similar to a review invite for surveys.
flow_id: unique identifier for the survey flow
flow_uid: unique identifier for the survey flow
location_uid: unique identifier for the organization
location_name:
organization_uid: unique identifier for the organization
organization_name
feedback_interaction_started_at: date survey was started
feedback_interaction_score: score of the survey
feedback_interaction_phone_number: phone number where survey was sent
feedback_interaction_customer_name: customer sent survey
response_inserted_at: date of customer response
response_body: response message from customer
flow_name: name of survey
flow_scale_min_score: min score a customer could respond to survey
flow_scale_max_score: max score a customer could respond to survey
flow_scale_score_type: type of survey flow
Table: Messages
Data Definitions
conversation_uid: unique identifier for the conversation
organization_uid: the unique identifier for the organization
organization_name: name of the organization
location_name: the name associated with the location
location_uid: the unique identifier for the location
contact_channel_uid: unique identifier for the contact channel
conversation_originated_from: Tracks the first conversation item originated from when the conversation is inbound initiated.
conversation_assigned_user_uid: the unique identifier for the assigned user for the conversation
conversation_is_inbound_initiated: flag indicating if the conversation was initiated by inbound messaging
conversation_channel_type: The channel that the conversation takes place in. Takes on values such as `phone`, `email`, or `secure`.
conversation_inserted_at: the date the conversation started
conversation_is_closed: flag indicating if the conversation has been closed
inbox_name: name of the inbox
inbox_type: type of the inbox
conversation_item_uid: unique identifier for the conversation item
conversation_item_sender_name: name of the sender for the conversation item
conversation_item_type:
conversation_item_body:
conversation_item_attachment_content_type:
conversation_item_inserted_at:
conversation_item_source_type:
conversation_item_delivery_status:
user_uid:
conversation_item_delivery_status:
Table: Payments
Data Definitions
invoice_uid: unique identifier for the invoice
invoice_requester:
invoice_number: number associated with the invoice
invoice_name: name associated with the invoice
customer_name: name associated with the customer
contact_identifier:
invoice_amount_dollars: the dollar amount of the invoice
invoice_inserted_at: the date the invoice was inserted
payment_inserted_at: the date the payment was inserted
organization_uid: the unique identifier for the organization
organization_name: the name associated with the organization
location_name: the name associated with the location
location_uid: the unique identifier for the location
contact_type: the type of the contact
Table: Leads
Data Definitions
organization_uid: unique identifier for the organization
organization_name: name of the organizaiton
location_uid: unique identifier for the location
location_name: name of the location
contact_channel_uid: unique identifier for the contact channel
conversation_originated_from: Tracks the first conversation item originated from when the conversation is inbound initiated.
conversation_assigned_user_uid: the unique identifier for the assigned user for the conversation
conversation_first_response_sent_at: the date of the first response that was sent
conversation_adjusted_first_response_time_seconds: Time it took, in seconds, for the first response to go out after receiving an inbound message where the conversation is `inbound_initiated`. Adjusted for business hours set up in Admin meaning that after business close, no additional seconds counted towards response time.
conversation_unadjusted_first_response_time_seconds: Full time it took, in seconds, for the first response to go out after receiving an inbound message where the conversation is `inbound_initiated`.
conversation_channel_type: The channel that the conversation takes place in. Takes on values such as `phone`, `email`, or `secure`.
conversation_inserted_at: Timestamp when the conversation record was inserted into the Postgres database.
conversation_is_closed:
channel_unique_identifier: Most often the phone number of a contact. This is the identifier for the channel, so channels like Apple Chat or Facebook will have a key or hash value.
contact_name: the name of the contact
inbox_name: the name of the inbox
inbox type: A way to organize inboxes (i.e., `custom` and `reviews`).
conversation_first_inbound_message: The first message on an inbound-initiated conversation.
conversation_first_webchat_url: The URL that the first Webchat message in a Webchat lead was sent from.
conversation_inbound_lead_converted_at: Timestamp of the review invite or feedback interaction used associated with the phone number at the organization where the lead started.
conversation_inbound_lead_converted_by: String indicating if the lead was converted after receiving a review invite (`review_invite`) or feedback interaction (`feedback_interaction`).
conversation_inbound_lead_converted_invite_uid: unique identifier for the inbound lead converted invite uid
time_to_convert_seconds: Time difference, in seconds, between when the lead started and when it received a review invite or feedback interaction.
Table: Campaign Contacts
Data Definitions
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
location_uid: unique identifier for the location.
location_name: name of the location.
partner_uid: unique identifier for the partner group.
contact_uid: unique identifier for the contact.
contact_name: name of the contact.
contact_phone_number: phone number of the contact.
last_campaign_at: the timestamp of the last campaign that a contact received.
contact_opt_in_tags: different tags used to group how the contact opted in.
contact_opt_in_source: the channel type that a contact opted in to receive campaign messages. values include upload, onboarding, payments, sms_message, webchat, banner, reviews, and opt_in_page.
contact_opted_in_at: timestamp of when the contact opted in.
contact_opted_out_at: timestamp of when the contact opted out of receiving future campaign messages.
contact_channel_type: the channel type that the contact uses. The only value at this point is phone.
Table: Campaigns
Data Definitions
location_uid: unique identifier for the location.
location_name: name of the location.
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
partner_uid: unique identifier for the partner group.
campaign_name: the in-app name of the campaign.
campaign_uid: unique identifier for a campaign.
campaign_message: the message used in the campaign.
campaign_started_at: timestamp when the campaign started.
campaign_ended_at: timestamp when the campaign ended.
campaign_status: indicates the status of the campaign including completed, in_progress, scheduled, system_draft, draft, inactive, active, and stopped.
contact_uid: unique identifier for a contact.
contact_name: name of the contact.
contact_phone_number: phone number for a contact.
campaign_interaction_uid: unique identifier for the campaign interaction.
campaign_interaction_at: timestamp for a campaign interaction.
campaign_interaction_type: tracks different types of interactions including sent, opt_out, failed, resubscribe, queued, link_clicked, and response.
Tip: To calculate which campaigns successfully sent from the core_campaigns models and which did not:
campaigns as (
select organization_uid
, location_uid
, contact_uid
, contact_phone_number
, campaign_name
, campaign_uid
, min(campaign_interaction_uid) as campaign_interaction_uid
, min(campaign_interaction_at) as campaign_interaction_at
from BUILD.campaigns.core_campaign_interactions
where campaign_interaction_type in ('failed', 'sent')
group by organization_uid, location_uid, contact_uid, contact_phone_number, campaign_name, campaign_uid
having max(case when campaign_interaction_type = 'failed' then 1 else 0 end) = 0 )
Table: Contacts
Data Definitions
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
partner_uid: unique identifier for the partner group.
contact_uid: unique identifier for the contact.
contact_name: name of the contact.
contact_channel_inserted_at: timestamp of when the record was added to the podium database.
channel_unique_identifier: unique identifier for a channel. This is most often a phone number.
contact_channel_opted_out_at: timestamp of when the contact opted out from receiving messages through this channel.
contact_channel_type: the channel type including phone, secure, email.
contact_channel_marketing_opted_out_at: timestamp of when the contact opted out of receiving marketing messages through this channel.
contact_channel_marketing_opted_in_at: timestamp of when the contact opted in to receive marketing messages through this channel.
contact_channel_marketing_opted_in_source: identifies which channel the contact opted in to receive marketing messages from podium (i.e., webchat).
Table: Location and Organizations
Data Definitions
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
organization_created_at: timestamp of when the organization was created in the podium database.
partner_uid: unique identifier for the partner group.
location_uid: unique identifier for the location.
location_name: name of the location.
location_created_at: timestamp of when the location was created in the podium database.
location_address: address of the location.
location_podium_number: podium number for the location that is used for texting.
location_phone_number: listed phone number for the location.
account_guid_c: the unique id trane uses to connect org_uid to their system.
Table: Reviews
Data Definitions
partner_uid: unique identifier for the partner group.
location_uid: unique identifier for the location.
location_name: name of the location.
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
listing_site: the name of the site.
review_uid: unique identifier for the review.
review_author: the name of the person who left the review.
review_rating: the rating on the review.
review_body: the text of the review.
review_published_at: the timestamp of when the review was published.
first_attributed_review_invite_uid: the first unique identifier for the review invite that the review can be attributed back to.
Tip: To calculate the conversion rates for reviews:
Join the reviews model to the review_invites model on first_attributed_review_invite_uid = review_invite_uid
Table: Review Invites
Data Definitions
partner_uid: unique identifier for the partner group.
review_invite_uid: Unique identifier for a review invite.
organization_uid: unique identifier for the organization.
organization_name: name of the organization.
location_uid: unique identifier for the location.
location_name: name of the location.
review_invite_channel: the way in which the review invite was delivered. For example email, text, apple, google_brand, and secure.
review_invite_sender_name: the name of the individual or integration that sent the review.
review_invite_sender_uid: the unique identifier of the sender. Could be a user uid or an integration uid, which would be determined using the ‘review_invite_sender_type’ field.
review_invite_customer_name: the name of the end consumer receiving the review invite.
review_invite_email: email of the individual receiving the invite, if sent through email.
review_invite_phone_number: the phone number of the end consumer receiving the review invite.
review_invite_sender_type: represents if an invite was sent through an integration or by a user. Null values are assumed to be 'user'.
review_invite_sent_at: timestamp of when the review invite was sent.
review_invite_sent_through: how the invite was sent including values such as client_app, generated_link_only, and integrations.
review_invite_clicked_at: Timestamp of when the end customer clicked the link in the review.
review_invite_is_integrated: identifies if the review invite was sent through an integration.
