Customer Stories is a multi-tenant B2B marketing automation platform that provides tools for crowdsourcing, curating, publishing, promoting, and analyzing the reach and audience of customer success stories. The typical target user is a client company's Customer Reference Program Manager.
- Import with CSV file or Zapier
- Manual data entry also available
- Invite contributors with factory-suggested or custom email templates
- Assign contributor prompts/questions to templates
- Import responses directly into stories
- Customer Story components: highlighted customer quote, video, highlighted metrics/results, story narrative (crafted via HTML WYSIWYG), call-to-action links/forms, related stories
- Stories on company page (e.g.
https://exampleinc.customerstories.net) are searchable and filterable via category and product tags - Publish levels: logo, preview, story
- Social media sharing
- SEO
- Published stories automatically uploaded to Google Ads
- Enable/pause ads via dashboard panel
- NOTE that ad blockers may detect Google markup on the ads preview page and block content. The page only mimics Google Ads content and does not load anything from Google. Disable your ad blocker to ensure all content loads
- Track visitors to stories over time
- Track source of visit (promotion, direct link, etc)
- Monitor recent activity, including new/imported data
- Google Charts
- Multiple configurable types: grid, carousel, tabbed carousel
- Customize featured stories
- postgreql
- node
- yarn
- Heroku CLI
- AWS CLI
- models:
Visitor,VisitorSession,VisitorAction,PageView,StoryShare - Regular updates via Heroku Scheduler and rake tasks are no longer active
- Console
- A separate user
csp-useris used to generate credentials for interacting with the S3 bucket from the application. See the IAM Management Console. - In the production S3 bucket, note the bucket policy which is necessary for the Cloudfront distribution to read from the bucket, and the CORS list which is necessary for user uploads and font requests.
- Public access to the production S3 bucket (used by both
.organd.net) is blocked, however since the development environment does not request assets through Cloudfront, public access to the development S3 bucket must be turned on. The bucket policy ensures only requests from development domains are allowed. - For the Cloudfront distribution, the only additional steps beyond creating the distribution (and accepting default values) were
- Creating the origin access control via these steps
- Editing the default behavior to include Origin headers in the cache key (required for subdomains)
- Customer Stories app
- test spreadsheets
- models:
AdwordsCampaign,AdwordsAdGroup,AdwordsAd,AdwordsImage