Klaviyo: Campaigns

Description

• Table of unique campaign versions. A campaign with 2 variations will have 2 distinct rows. Counts of the unique users and instances of the events, as well as sums of the numeric value associated with events (i.e. revenue) will be pivoted out into columns, as configured by the klaviyo__count_metrics and klaviyo__sum_revenue_metrics variables, respectively. See the dbt_project.yml file for the default metrics used. These columns will be prefixed with count_, unique_count_, and sum_revenue_.

Supported Data Sources

• Klaviyo

Columns

Type	Name	Description
STRING	campaign_type	Type of campaign.
DATETIME	created_at	Timestamp of when the campaign was created, in UTC.
STRING	email_template_id	Foreign key referencing the ID of the email_template object that will be the content of this campaign. Note the Email Template is copied when creating this campaign, so future changes to that Email Template will not alter the content of this campaign.
STRING	from_email	The email address your email will be sent from and will be used in the reply-to header.
STRING	from_name	The name or label associated with the email address you're sending from.
STRING	campaign_id	Unique ID of the campaign.
STRING	campaign_name	A name for this campaign. If not specified, this will default to the subject of the campaign.
DATETIME	scheduled_to_send_at	Timestamp of when the campaign is scheduled to be sent in the future, if "smart send time" is used.
DATETIME	sent_at	Timestamp of when the campaign was first sent out to users.
STRING	status	Current status of the campaign. Either "draft", "scheduled", "sent", or "cancelled".
STRING	status_id	Corresponding ID to the current status.
STRING	subject	The subject line of the campaign's email.
DATETIME	updated_at	Timestamp of when the campaign was last updated.
BOOLEAN	is_archived	Boolean of whether the campaign has been archived or not
DATETIME	scheduled_at	The datetime when the campaign was scheduled for future sending
STRING	source_relation	The source where this data was pulled from. If you are making use of the union_schemas variable, this will be the source schema. If you are making use of the union_databases variable, this will be the source database. If you are not unioining together multiple sources, this will be an empty string.
STRING	variation_id	Unique ID of the attributed campaign variation group. This does not map onto another table.
INTEGER	total_count_unique_people	The count of the distinct people that have interacted with this campaign.
DATETIME	first_event_at	Timestamp of the first ever interaction between this campaign and a person.
DATETIME	last_event_at	Timestamp of the most recent interaction between this campaign and a person.
INTEGER	sum_revenue_refunded_order
INTEGER	sum_revenue_placed_order
INTEGER	sum_revenue_ordered_product
INTEGER	sum_revenue_checkout_started
INTEGER	sum_revenue_cancelled_order
INTEGER	count_active_on_site
INTEGER	unique_count_active_on_site
INTEGER	count_viewed_product
INTEGER	unique_count_viewed_product
INTEGER	count_ordered_product
INTEGER	unique_count_ordered_product
INTEGER	count_placed_order
INTEGER	unique_count_placed_order
INTEGER	count_refunded_order
INTEGER	unique_count_refunded_order
INTEGER	count_received_email
INTEGER	unique_count_received_email
INTEGER	count_clicked_email
INTEGER	unique_count_clicked_email
INTEGER	count_opened_email
INTEGER	unique_count_opened_email
INTEGER	count_marked_email_as_spam
INTEGER	unique_count_marked_email_as_spam
INTEGER	count_unsubscribed
INTEGER	unique_count_unsubscribed
INTEGER	count_received_sms
INTEGER	unique_count_received_sms
INTEGER	count_clicked_sms
INTEGER	unique_count_clicked_sms
INTEGER	count_sent_sms
INTEGER	unique_count_sent_sms
INTEGER	count_unsubscribed_from_sms
INTEGER	unique_count_unsubscribed_from_sms
STRING	campaign_variation_key	Unique key hashed on the campaign and variation IDs.