Content concepts across channels
See which social content receives a response.
Review content, campaign, channel, post and engagement together where identifiers and provider observations support the connection. Traffic and conversion need separate analytics evidence; social engagement alone does not establish either.
Interactive Capability Preview
Illustrative workflow with sample telemetry. Real captures appear on the homepage.
How the capability works
Seven parts of a useful comparison
Use these seven concepts to review which content ideas receive a response across channels. The observation API does not automatically join all seven into an attribution report.
- Content — connect a campaign asset where an asset identifier is recorded; a full content-concept map is not inferred
- Campaign — review the recorded campaign identifier and its scoped objective
- Channel — preserve the provider and integration context when comparing channels
- Post — use the provider post identifier and publication timestamp where available
- Engagement — provider-observed metrics such as impressions, reach, views, clicks, comments and shares; missing metrics stay missing
- Traffic — needs connected analytics observations and matching identifiers; provider clicks are not verified site visits
- Conversion — needs recorded conversion events, attribution evidence and a defined window; engagement is not proof of conversion
Keep source, identifiers and window visible
Social observations retain provider, integration, channel, post and campaign identifiers, an optional asset identifier, capture time and publication time where available. The read API supports capture-time from/to filters, channel, campaign, asset and cursor pagination. Comparing results requires compatible metric definitions and time windows.
- The dashboard shows the latest snapshot per provider/post in the loaded observations; this is not every post, full history or a global total
- Matching a campaign or asset identifier helps review relationships; it does not prove that a post caused traffic or conversions
- Report missing coverage, unmatched identifiers and incompatible windows before comparing content concepts
Observed data, explicit limits
Observations require a configured analytics repository and authorized supported source. The sync path checks a published campaign post, its connected social account, source capability and scope. Available metrics vary by provider. Missing traffic or conversion evidence stays unavailable, never estimated from engagement. Correlation is not causation.
Frequently asked implementation questions
Does social analytics prove which post converted a visitor?
No. The social observation API stores provider metrics and identifiers, not an automatic traffic/conversion join. Review separate connected analytics, recorded events, matching IDs and the attribution window. A plausible relationship is not causal proof.
Want to see what your site is missing?
Connect your domain, inspect the evidence, and use Groviqo to prioritize the next growth moves.
Start at your pace. Connect your data sources, surface high-impact opportunities, and execute improvements with total control.