Add documentation for Looker Studio setup#590
Merged
mahajantejas merged 5 commits intomainfrom Apr 16, 2026
Merged
Conversation
Document the steps to set up Looker Studio for WhatsApp Groups Automation, including prerequisites, SQL queries, and dashboard replication instructions.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughNew beginner documentation page added that explains how to set up and replicate a Looker Studio dashboard for WhatsApp Groups Automation using Glific BigQuery data, including prerequisites, a BigQuery SQL workflow to create a Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚀 Deployed on https://deploy-preview-590--glific-docs.netlify.app |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/6`. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp
Groups Automation.md:
- Line 15: Summary: Fix compound modifier hyphenation in the document by
updating two phrases; change the phrase "program specific outputs/outcomes
tracking" to "program-specific outputs/outcomes tracking" and change "weekly
patterns" (as used in the context "weekly patterns and errors") to "week-on-week
patterns and errors" so compound modifiers are hyphenated correctly; update
those exact strings in the document where they appear.
- Line 110: The doc has a typo/unclosed backtick in the view name: replace the
incorrect `group_poll (singular and unclosed) with the correct inline code
`group_polls` (plural, properly closed) so the instruction "save the view as
`group_polls`" matches the rest of the document and fixes the broken inline
formatting; update the text that currently contains `group_poll to use
`group_polls` instead and ensure the backticks are balanced.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8ee94e92-6b59-45ba-be45-c95f7bf339a3
📒 Files selected for processing (1)
docs/6. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp Groups Automation.md
Corrected minor grammatical issues and formatting in the documentation.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
docs/6. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp Groups Automation.md (1)
110-110:⚠️ Potential issue | 🟡 MinorFix sentence grammar in the “save view” instruction.
Current phrasing (“save it in under”) is awkward and easy to misread during setup.
Suggested doc fix
- d) Save the query as a “View”, save it in under the same dataset and name the view as `group_polls` + d) Save the query as a “View”, save it under the same dataset, and name the view `group_polls`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/6`. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp Groups Automation.md at line 110, Replace the awkward sentence "Save the query as a “View”, save it in under the same dataset and name the view as `group_polls`" with a clearer instruction such as: "Save the query as a 'View' in the same dataset and name the view `group_polls`." Update the line that mentions `group_polls` accordingly to ensure clarity and correct grammar.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/6`. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp
Groups Automation.md:
- Line 34: Change the wording in step 2 to use the singular "view" instead of
"tables" to avoid confusion—update the sentence "Set up the `group_polls`
tables" to "Set up the `group_polls` view" (the referenced symbol is
`group_polls`) and ensure any surrounding text that refers to multiple tables is
adjusted to reflect that a single view is being created.
- Line 166: Replace the typo "Total going texts" with "Total outgoing texts" in
the bullet list under the "Setting up Lookerstudio for WhatsApp Groups
Automation" section (search for the exact string "Total going texts" and update
it to "Total outgoing texts" to keep wording consistent).
- Around line 50-51: The deduplication using "PARTITION BY wa_group_name, body"
+ "ORDER BY inserted_at DESC" currently retains only the latest poll with
identical text per group—either document this behavior explicitly (add a note
near the SQL snippet stating “This keeps only the latest message per identical
question text in each group”) or change the partition key to include a unique
identifier (e.g., use message_id or inserted_at with wa_group_name) if you want
every repeated poll tracked; also fix the wording inconsistencies by replacing
"tables" with "view" (line ~34), changing "save it in under" to "save it in"
(line ~110), and correcting "Total going texts" to "Total outgoing texts" (line
~166).
---
Duplicate comments:
In `@docs/6`. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp
Groups Automation.md:
- Line 110: Replace the awkward sentence "Save the query as a “View”, save it in
under the same dataset and name the view as `group_polls`" with a clearer
instruction such as: "Save the query as a 'View' in the same dataset and name
the view `group_polls`." Update the line that mentions `group_polls` accordingly
to ensure clarity and correct grammar.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 82f2ca5f-f4ab-4749-9b65-413e5d00e2d3
📒 Files selected for processing (1)
docs/6. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp Groups Automation.md
Comment on lines
+50
to
+51
| PARTITION BY wa_group_name, body | ||
| ORDER BY inserted_at DESC |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
fd -t f "Setting up Lookerstudio for WhatsApp Groups Automation.md"Repository: glific/docs
Length of output: 147
🏁 Script executed:
cat -n "docs/6. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp Groups Automation.md"Repository: glific/docs
Length of output: 8178
Clarify the dedup intent — PARTITION BY wa_group_name, body silently drops repeated poll questions.
The current dedup keeps only the latest poll message per unique question text in each group. If the dashboard should track all polls (including when the same question is asked multiple times), change the dedup key. If only the latest instance matters, document this design choice explicitly.
Fix wording inconsistencies:
- Line 34: Change "tables" to "view"
- Line 110: Change "save it in under" to "save it in"
- Line 166: Change "Total going texts" to "Total outgoing texts"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/6`. WhatsApp Groups Automation/Setting up Lookerstudio for WhatsApp
Groups Automation.md around lines 50 - 51, The deduplication using "PARTITION BY
wa_group_name, body" + "ORDER BY inserted_at DESC" currently retains only the
latest poll with identical text per group—either document this behavior
explicitly (add a note near the SQL snippet stating “This keeps only the latest
message per identical question text in each group”) or change the partition key
to include a unique identifier (e.g., use message_id or inserted_at with
wa_group_name) if you want every repeated poll tracked; also fix the wording
inconsistencies by replacing "tables" with "view" (line ~34), changing "save it
in under" to "save it in" (line ~110), and correcting "Total going texts" to
"Total outgoing texts" (line ~166).
Collaborator
Author
|
@mahajantejas Please review this. |
… WhatsApp Groups Automation.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
mahajantejas
approved these changes
Apr 16, 2026
mahajantejas
deleted the
Setting-up-Lookerstudio-for-WhatsApp-Groups-Automation.md
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document the steps to set up Looker Studio for WhatsApp Groups Automation, including prerequisites, SQL queries, and dashboard replication instructions.
Summary by CodeRabbit