Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
291 changes: 291 additions & 0 deletions markdown/blog/2025-Q2-marketing-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,291 @@
---
title: "AsyncAPI Q2 Marketing WG Report"
date: 2025-05-27T06:00:00+01:00
type: Communication
tags:
- Project Status
- Marketing
cover: /img/posts/marketing-images/marketing-q1-report.webp
authors:
- name: Atinuke Oluwabamikemi Kayode
photo: /img/avatars/bami.webp
link: https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/
byline: AsyncAPI Community Marketing Specialist
excerpt: "This Q2 report highlights AsyncAPI’s marketing efforts across community engagement, events, and platform growth."
---

In Q2, the AsyncAPI Marketing Working Group focused on expanding visibility, increasing engagement, and driving participation across our channels. With three major conferences in the pipeline—Singapore, Munich, and Lagos—our activities were centered around community outreach, event promotion, and contributor support.

This report outlines the key marketing activities executed, highlights performance metrics across platforms, and provides insights into what worked, what didn’t, and where we’re heading in Q3.

## Key Objectives

- Enhance global awareness of AsyncAPI, especially in Asia (Singapore) and Africa (Lagos)

- Drive high-quality CFP submissions and attendee diversity for Singapore, Munich, Lagos events

- Deepen community engagement across LinkedIn, X, Slack, and newsletter

- Promote the community members and expand content marketing via spotlight stories

- Introduce the Webinar Initiative.

## Strategy Alignment

All Q2 activities were implemented to advance the approved [Community Marketing Strategy](https://github.com/asyncapi/community/blob/master/docs/030-project-vision-strategy-goals/2025_marketing_strategy.md). Below we map Q2 actions to each strategic goal, evidence from Q2, and recommended next steps.

### Goal 1 — Encourage Adoption of AsyncAPI & EDA

**Q2 Activities**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Fix markdownlint MD036: use headings instead of bold for section labels

Bold text is used as headings; convert to proper heading levels for structure and lint compliance.

-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Gap/Next steps**
+#### Gaps and next steps
-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Next steps**
+#### Next steps
-**Q2 Activities**
+#### Q2 Activities
-**Evidence**
+#### Evidence
-**Next steps**
+#### Next steps
-**Recomendation**
+#### Recommendations
-**User Engagement Insights (Google Analytics)**
+#### User Engagement Insights (Google Analytics)
-**High Traffic, Low Engagement**
+#### High Traffic, Low Engagement
-**High Engagement, Lower Traffic**
+#### High Engagement, Lower Traffic
-**Low Traffic, Moderate Engagement**
+#### Low Traffic, Moderate Engagement
-**Notable Drops**
+#### Notable Drops
-**Key Insights**
+#### Key Insights

Also applies to: 47-47, 54-54, 61-61, 65-65, 71-71, 78-78, 84-84, 90-90, 96-96, 159-159, 161-161, 171-171, 183-183, 193-193, 203-203

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

39-39: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 39, 47, 54, 61, 65, 71,
78, 84, 90, 96, 159, 161, 171, 183, 193, and 203, replace bold text used as
section labels with proper markdown headings by adding appropriate heading
markers (#) to improve document structure and comply with markdownlint MD036.


- AsyncAPI track at APIDays Singapore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Branding, capitalization, and event copy fixes

  • APIdays brand capitalization.
  • Clearer wording for CFP promotions.
  • Subject-verb agreement and brand casing.
  • Consistent capitalization for “Key Insight”.
-- AsyncAPI track at APIDays Singapore
+- AsyncAPI track at APIdays Singapore
-### X (Twitter) Key insight
+### X (Twitter) Key Insight
-- Organized a spotlighted AsyncAPI track at APIDays Singapore.
+- Organized a spotlighted AsyncAPI track at APIdays Singapore.
-- May–June promotion focused on Bangalore CFP Munich and Lagos conference.
+- May–June promotion focused on CFPs for Munich and Lagos conferences.
-- Paris, Developerweek, and Online CFP is now open
+- Paris, DeveloperWeek, and online CFPs are now open

Also applies to: 233-233, 239-241, 145-145

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 41, 145, 233, and 239-241,
fix branding and capitalization issues by correcting "APIdays" to the proper
brand capitalization "APIDays," improve clarity in CFP promotion wording, ensure
subject-verb agreement, and maintain consistent capitalization for the phrase
"Key Insight." Review these lines carefully and update the text accordingly to
align with the brand and style guidelines.


- The "Learn With AsyncAPI" webinar series documentation has been merged and the first session is on the 30th of September.

- Conference workshops and hands-on sessions
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't recall us having these


**Evidence**

- Strong in-person attendance in Singapore
- Webinar engagement and repurposed content
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it evidence we have or we plan to have as a measure?

- Newsletter open rate of 42%;
- AsyncAPI Singapore recap video (1.8k views).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

link to video please


**Gap/Next steps**

Multilingual documentation target (one translation by end of Q2) was planned in the strategy, work was but has not been initiated.
Recommend prioritizing at least one translated guide, and preparing localized workshop materials for Lagos.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are the localized workshop materials for Lagos?


### Goal 2 — Showcase Exceptional Talent

**Q2 Activities**

Community spotlights, newsletter features highlighting maintainers and first-time speakers, and a CFP drive focused on diverse representation.

**Evidence**

- CFP submissions: Munich — 63 (40% new speakers)
- Lagos — 48 (100% Africa-based; 60% women-led).
- Increased engagement on spotlight posts and positive community feedback.

**Next steps**

- Publish in-depth case studies and maintainership stories
- Encourage the community members to make use of the holopin badges recognition program to surface high-impact contributors.

### Goal 3 — Drive Community Engagement & Contribution

**Q2 Activities**

- Increased social posting cadence (LinkedIn: 78 posts, +63%)

- Active Slack channels around events

**Evidence**

- LinkedIn impressions +104%, clicks +101%, engagement rate 8.06%

- Slack growth +9.4%; newsletter subscriber growth +7.3%.

**Next steps**

- Scale the Student Ambassador Program promotion and onboarding (Q3 focus)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not merged, nor in progress? I would pause this initiative, I personally don't think it is needed atm, would leave it for new board to discuss


- Implement quarterly contributor surveys to close feedback loops.

**Recomendation**

- Targeted email campaigns

- AMAs and interactive webinars.

## Marketing Working Group Performance Overview

### Social Media & Community Performance

| **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**|
|---------|-------------|-----------|-----------|-------------|
LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please improve columns description to explain what the numbers replresent, for example what 4,249 is, is it impression, views, engagement or what exactly

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly
LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled, click-throughs and engagement increased significantly

X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets
Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep
Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark

Comment on lines +106 to +112
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix markdownlint MD055: add leading/trailing pipes and polish copy in the summary table

The table is missing leading/trailing pipes and has a punctuation issue on the LinkedIn row.

-| **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**|
-|---------|-------------|-----------|-----------|-------------|
-LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly
-X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets
-Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep
-Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark
+| Platform   | Start of Q2 | End of Q2 | % Change | Key Insights |
+|------------|-------------|-----------|----------|--------------|
+| LinkedIn   | ~4,249      | 4,534     | +7%      | Strong post cadence (78 posts); impressions doubled; click-throughs and engagement increased significantly |
+| X (Twitter)| 4,732       | 4,759     | +0.57%   | Increased tweet output and engagement. Slight dip in new followers and retweets |
+| Slack      | 6,889       | 7,098     | +3.03%   | Community chats intensified around GSoC and event prep |
+| Newsletter | ~6.8k       | ~7.3k     | +7.3%    | Open rate ~42%, CTR above industry benchmark |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| **Platform** | **Start of Q2** | **End of Q2** | **% Change** | **Key Insights**|
|---------|-------------|-----------|-----------|-------------|
LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts), impressions doubled.click-throughs and engagement increased significantly
X (Twitter) | 4732 | 4759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets
Slack | 6889 | 7098 | +3.03% | Community chats intensified around GSOC and event prep
Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark
| Platform | Start of Q2 | End of Q2 | % Change | Key Insights |
|------------|-------------|-----------|----------|--------------|
| LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence (78 posts); impressions doubled; click-throughs and engagement increased significantly |
| X (Twitter)| 4,732 | 4,759 | +0.57% | Increased tweet output and engagement. Slight dip in new followers and retweets |
| Slack | 6,889 | 7,098 | +3.03% | Community chats intensified around GSoC and event prep |
| Newsletter | ~6.8k | ~7.3k | +7.3% | Open rate ~42%, CTR above industry benchmark |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 106 to 112, the
markdown table lacks leading and trailing pipe characters on each line, which is
required for proper table formatting. Additionally, the LinkedIn row has a
punctuation issue where a period is missing between "impressions doubled" and
"click-throughs." Add the missing leading and trailing pipes to every table row
and insert the missing period to correct the punctuation in the LinkedIn row.

| **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** |
|:------------|:-----------|:-------------|:---------------|
Followers | 4,534 | 4,255 | (+7%) |
New Followers| 285 | 313 | (-7%) |
Posts | 78 | 48 | (+63%) |
Impressions | 48,443 | 23,715 | (+104%) |
Clicks | 3,007 | 1,495 | (+101%) |
Engagement Rate | 8.06% | 7.52% | (+11%) |

Comment on lines +106 to +121
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Frontmatter and blog schema parity check with existing posts

Please verify that frontmatter keys (type, tags, authors, cover) match existing blog conventions (some posts use author vs authors, different type values). Also ensure tables render properly on the site theme.

Also applies to: 134-144, 1-15


🏁 Script executed:

#!/bin/bash
# Compare frontmatter patterns against existing blog posts
fd -e md markdown/blog | xargs -I{} sh -c '
  echo "== {} ==";
  head -n 30 "{}" | sed -n "1,30p" | rg -n "^(title|date|type|tags|cover|author|authors):"
'

echo
echo "Check common values for \`type:\`"
rg -n "^type:\s" markdown/blog | cut -d: -f3 | sort | uniq -c

echo
echo "Sample a known marketing report for reference (if present):"
fd -e md "marketing" markdown/blog | xargs -I{} sh -c 'echo "-- {} --"; head -n 30 "{}"'

Length of output: 6054


Frontmatter keys are consistent; tables need proper row delimiters

I’ve verified that the frontmatter in 2025-Q2-marketing-report.md (lines 1–15) uses the same keys as other marketing reports (title, date, type: Communication, tags, cover, authors, excerpt), so no changes are needed there.

However, to ensure both tables render correctly under our site theme, please update the markdown so every data row starts and ends with a pipe. For example:

  • In the first table (lines 106–121), change

    LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence…
    

    to

    | LinkedIn | ~4,249 | 4,534 | +7% | Strong post cadence… |
    
  • Apply the same leading/trailing | to all rows in the second table (lines 134–144).

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


108-108: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


109-109: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


110-110: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing leading pipe

(MD055, table-pipe-style)


111-111: Table pipe style
Expected: leading_and_trailing; Actual: no_leading_or_trailing; Missing trailing pipe

(MD055, table-pipe-style)


115-115: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


116-116: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


117-117: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


118-118: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


119-119: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


120-120: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md between lines 106 and 121, the
tables lack leading and trailing pipe characters on each data row, which can
cause rendering issues. Update every row in both tables to start and end with a
pipe character (|), ensuring consistent markdown table syntax for proper display
under the site theme.

Comment on lines +113 to +121
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Fix markdownlint MD055: add leading/trailing pipes to LinkedIn metrics table

Rows are missing leading pipes. Add pipes for consistency and lint compliance.

-| **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** |
-|:------------|:-----------|:-------------|:---------------|
-Followers    |   4,534     | 4,255     | (+7%)    |
-New Followers|  285     | 313     |  (-7%)    |
-Posts | 78       | 48        | (+63%)    |
-Impressions | 48,443  |       23,715 |       (+104%) | 
-Clicks |    3,007 |      1,495 |        (+101%)  |
-Engagement Rate |  8.06% |  7.52%     | (+11%)  |
+| LinkedIn Performance | Value | Last Quarter Value | % Change |
+|:---------------------|:------|:-------------------|:---------|
+| Followers            | 4,534 | 4,255              | (+7%)    |
+| New Followers        | 285   | 313                | (-7%)    |
+| Posts                | 78    | 48                 | (+63%)   |
+| Impressions          | 48,443| 23,715             | (+104%)  |
+| Clicks               | 3,007 | 1,495              | (+101%)  |
+| Engagement Rate      | 8.06% | 7.52%              | (+11%)   |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| **LinkedIn Performance** | **Value** | **Last Quarter Value** | **% Change** |
|:------------|:-----------|:-------------|:---------------|
Followers | 4,534 | 4,255 | (+7%) |
New Followers| 285 | 313 | (-7%) |
Posts | 78 | 48 | (+63%) |
Impressions | 48,443 | 23,715 | (+104%) |
Clicks | 3,007 | 1,495 | (+101%) |
Engagement Rate | 8.06% | 7.52% | (+11%) |
| LinkedIn Performance | Value | Last Quarter Value | % Change |
|:---------------------|:------|:-------------------|:---------|
| Followers | 4,534 | 4,255 | (+7%) |
| New Followers | 285 | 313 | (-7%) |
| Posts | 78 | 48 | (+63%) |
| Impressions | 48,443| 23,715 | (+104%) |
| Clicks | 3,007 | 1,495 | (+101%) |
| Engagement Rate | 8.06% | 7.52% | (+11%) |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

115-115: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


116-116: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


117-117: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


118-118: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


119-119: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


120-120: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 113 to 121, the
LinkedIn metrics table rows are missing leading pipes, which violates
markdownlint rule MD055. Add a leading pipe character at the start of each row
to ensure consistent table formatting and compliance with markdownlint.

### LinkedIn Key Insight
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like these insignts, but missing deep dive into specific posts. What is our learning here?

  • is it that some specific type of posts engage more?
  • or is it posts with pictures
  • or is it the time they are published? like majority of stuff published on Tuesday are move visible?
  • or maybe the only answer is, if you want more engagement, visibility and followers, you should produce much more content - doesn't matter when and what?

I'm also very much interested with our youtube, expecially the educational content with Ace. How promotion of it work, what we learned? maybe we should "repromote", like not share it once and forget, but write about it, in different style, once a month? with shorts, maybe with video shared directly in LinkedIn? not as a YT link


This quarter, LinkedIn became our strongest growth engine, reflecting the success of our content strategy in driving professional engagement and industry visibility.

- Our follower base grew to 4,534 (+7%), adding 285 new followers despite a 7% dip compared to last month’s gains, a sign that while our growth pace slowed, audience quality remains high.

- With 78 posts published (+63%), we more than doubled our content output, leading to 48,443 impressions (+104%) and 3,007 clicks (+101%).

- The engagement rate reached 8.06% (+11%), showing that not only are we reaching more people, but our content resonates deeply with them.

Strategy alignment: Our push for thought leadership and value-driven content directly supported brand positioning as a trusted voice in the API and tech community.

**Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** |
|:------------|:--------------|:-------------|:----------|
Tweets | 119 | 89 | (+34%) |
Retweets | 21 | 24 | (-16%) |
Impressions | 17,500 | 14,621 | (+20%) |
Engagements | 280 | 278 | (+1%) |
Replies | 5 | 3 | (+67%) |
Clicks | 93 | 101 | (-7%) |
Likes | 110 | 93 | (+18%) |
New Followers| 27 | 36 | (-25%) |

Comment on lines +134 to +144
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Fix markdownlint MD055: add leading/trailing pipes to X (Twitter) metrics table

Rows are missing leading pipes.

-**Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** |
-|:------------|:--------------|:-------------|:----------|
-Tweets | 119  |  89  |  (+34%)  |
-Retweets |  21  |  24  |  (-16%)  |
-Impressions | 17,500 | 14,621 |  (+20%)  |
-Engagements |  280  |  278  |  (+1%) |
-Replies |  5  |  3  |  (+67%)  |
-Clicks |   93  |  101 |  (-7%)  |
-Likes |  110  |  93  | (+18%) |
-New Followers|   27  |  36  |  (-25%) |
+| Twitter/X Performance | Value | Last Quarter Value | % Change |
+|:----------------------|:------|:-------------------|:---------|
+| Tweets                | 119   | 89                 | (+34%)   |
+| Retweets              | 21    | 24                 | (-16%)   |
+| Impressions           | 17,500| 14,621             | (+20%)   |
+| Engagements           | 280   | 278                | (+1%)    |
+| Replies               | 5     | 3                  | (+67%)   |
+| Clicks                | 93    | 101                | (-7%)    |
+| Likes                 | 110   | 93                 | (+18%)   |
+| New Followers         | 27    | 36                 | (-25%)   |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Twitter/X Performance** | **Value** | **Last Quarter Value** | **% Change** |
|:------------|:--------------|:-------------|:----------|
Tweets | 119 | 89 | (+34%) |
Retweets | 21 | 24 | (-16%) |
Impressions | 17,500 | 14,621 | (+20%) |
Engagements | 280 | 278 | (+1%) |
Replies | 5 | 3 | (+67%) |
Clicks | 93 | 101 | (-7%) |
Likes | 110 | 93 | (+18%) |
New Followers| 27 | 36 | (-25%) |
| Twitter/X Performance | Value | Last Quarter Value | % Change |
|:----------------------|:------|:-------------------|:---------|
| Tweets | 119 | 89 | (+34%) |
| Retweets | 21 | 24 | (-16%) |
| Impressions | 17,500| 14,621 | (+20%) |
| Engagements | 280 | 278 | (+1%) |
| Replies | 5 | 3 | (+67%) |
| Clicks | 93 | 101 | (-7%) |
| Likes | 110 | 93 | (+18%) |
| New Followers | 27 | 36 | (-25%) |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

134-134: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


136-136: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


137-137: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


138-138: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


139-139: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


140-140: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


141-141: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


142-142: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)


143-143: Table pipe style
Expected: leading_and_trailing; Actual: trailing_only; Missing leading pipe

(MD055, table-pipe-style)

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md around lines 134 to 144, the
markdown table for Twitter/X performance metrics is missing leading pipes on
each row. Add a leading pipe character '|' at the start of every row in the
table to comply with markdownlint MD055 and ensure proper table formatting.

### X (Twitter) Key insight

X continues to be a space for timely updates and community conversations, though audience growth slowed this month.

- We published 119 tweets (+34%), which boosted impressions to 17,500 (+20%) and likes to 110 (+18%).

- Engagements (280, +1%) remained stable, while replies jumped by 67%, showing a stronger two-way conversation with the community.

- However, clicks dipped by 7% and new followers dropped by 25%, indicating that while interaction is happening, conversion to action and follower acquisition needs targeted focus.

Strategy alignment: The conversational engagement aligns with our community-first approach, but the drop in clicks and followers signals a need to balance interaction with calls-to-action and shareable content. Also we have decided to keep the automated tweets as they serve folks that are not on the Slack channel but still needs our spec and tools update.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Fix typos and grammar for clarity and professionalism

Addresses LanguageTool findings and general wording.

-Also we have decided to keep the automated tweets as they serve folks that are not on the Slack channel but still needs our spec and tools update.
+Also, we have decided to keep the automated tweets, as they serve folks who are not on the Slack channel but still need our spec and tools updates.
-### Website Performace
+### Website Performance
-### Slack Performace 
+### Slack Performance
-... first session is set to happen in September as everyone will be on summer holiday in the most part of Q3. [The initiative documetation was merged in June]...
+... first session is set to happen in September, as many will be on summer holiday for most of Q3. [The initiative documentation was merged in June]...
-Also, we took the libarty to create the [webinar planning template](...) that help us make sure we are on track with the planning and you can stay up-to-date with the webinar [here](...).
+Also, we took the liberty of creating the [webinar planning template](...), which helps us stay on track with planning; you can stay up to date with the webinar [here](...).

Also applies to: 157-157, 215-215, 221-221, 223-223

🤖 Prompt for AI Agents
In markdown/blog/2025-Q2-marketing-report.md at lines 155, 157, 215, 221, and
223, fix typos and improve grammar for clarity and professionalism. Review each
sentence for proper punctuation, subject-verb agreement, and consistent tense.
Rephrase awkward or unclear wording to enhance readability while maintaining the
original meaning.


### Website Performace
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the level of details here, but please can you also provide links to these pages?


**User Engagement Insights (Google Analytics)**

**High Traffic, Low Engagement**

- "AsyncAPI Initiative for event-driven APIs" (17.3% of total views, avg. time 15s, 0.2% engagement)

- This page draws the most visitors but fails to hold attention — very short dwell time suggests users either bounce quickly or don’t find the immediate content relevant.

- "3.0.0" (15.8% views, 38s avg. time, 4.9% engagement)

- Strong traffic, better than above in engagement, but still relatively low for such a key spec release page. Visitors may be skimming rather than deeply reading.

**High Engagement, Lower Traffic**

- "Understanding AsyncAPIs with a Practical Example" (3.1% views, 42s avg. time, 37.2% engagement)

- Excellent retention rate — users are staying longer and interacting more. Suggests practical, example-driven content resonates.

- Could be promoted more heavily to increase traffic.

- "2.6.0" (2.5% views, 55s avg. time, 36.5% engagement)

- Longest dwell time and high engagement percentage, meaning readers are highly interested in detailed version-specific updates.

**Low Traffic, Moderate Engagement**

- "AsyncAPI document structure" (2.9% views, 46s avg. time, 5.0% engagement)

- Decent retention but under-visited; likely valuable for users already in the documentation but not a strong entry point.

- "Generator" (2.9% views, 17s avg. time, 9.0% engagement)

- Users interact, but short reading time suggests they find what they need quickly — could be a tool download or copy-paste scenario.

**Notable Drops**

- "Tools" (2.4% views, 15s avg. time, 2.4% engagement)

- Both traffic and engagement are low — unclear value proposition or poor discoverability.

- "Usage" (2.0% views, 3s avg. time, 2.9% engagement)

- Very low dwell time; possibly confusing, too short, or misplaced in navigation.

**Key Insights**

- Practical, example-driven pages ("Understanding AsyncAPIs…", version release notes) keep people engaged the most.

- High-traffic pages ("AsyncAPI Initiative…", "3.0.0") need clearer, more engaging intros or calls-to-action to reduce bounce rates.

- Hidden gems like "AsyncAPI document structure" could be surfaced more in navigation and promotions.

- Low dwell time pages suggest quick reference or unclear purpose may need restructuring.

## Event and Community Engagement

### Slack Performace



### The AsyncAPI Webinar Initiative

The AsyncAPI Webinar Initiative is a recurring, live, and on-demand knowledge-sharing program designed to educate, inspire, and engage the global AsyncAPI community. It serves as a bridge between technical contributors, industry adopters, and curious newcomers, offering a structured way to disseminate updates, best practices, and real-world use cases of event-driven APIs. We have some folks in the pipeline and the first session is set to happen in September as everyone will be on summer holiday in the most part of Q3. [The initiative documetation was merged in June](https://github.com/asyncapi/community/blob/master/docs/070-marketing/webinar_series_initiative.md).

Also, we took the libarty to create the [webinar planning template](https://github.com/asyncapi/community/blob/master/docs/070-marketing/webinar_planning_template.md) that help us make sure we are on track with the planning and you can stay up-to-date with the webinar [here](https://github.com/asyncapi/community/issues/1993).

### Community Spotlight

Unfortunately, we couldn't publish the three stories meant for this quarter due to some blockers such as long review process for each blogs. This has made us initiate the bulk production of the stories for Q3.

### AsyncAPI Conference 2025

AsyncAPI Singapore (April 15–16)

- Organized a spotlighted AsyncAPI track at APIDays Singapore.

- Pre-event outreach via social content led to strong in-person attendance and post-event community onboarding.

- CFP Campaigns for Munich & Lagos

- May–June promotion focused on Bangalore CFP Munich and Lagos conference.

- Paris, Developerweek, and Online CFP is now open

## Top 3 Best-Performing Posts

These posts were selected based on their impressions and number of clicks.

1. [We’re thrilled to welcome 7 incredible contributors to the AsyncAPI community as part of Google Summer of Code 2025! 🎉](https://www.linkedin.com/feed/update/urn:li:share:7327603592150798336/)

- Impressions: 9,237
- Likes: 133
- Comments: 6
- Clicks: 821
- Eng. Rate: 10.48%

Key Insight: The high engagement rate of 10.48%—well above industry averages, shows that the content strongly resonated with the audience. The combination of 9,237 impressions, a notable 133 likes, and 821 clicks indicates not only strong visibility but also an active interest in taking further action, suggesting that similar content formats and topics could drive even higher conversions in future campaigns.

2.[Ankit Kumar, Head of Developer and Customer Success at,Aklivity is speaking on "AsyncAPI v3: Streamlining Event-Driven API Design"](https://www.linkedin.com/feed/update/urn:li:ugcPost:7318133926613401600/)

- Impressions: 1,856
- Likes: 73
- Comments: 1
- Clicks: 512
- Eng. Rate: 31.63%

Key Insight: With an exceptional 31.63% engagement rate, this post achieved deep audience connection despite lower impressions (1,856) compared to other top posts. The high click-through volume (512 clicks) shows the content was highly compelling and action-oriented, making it a strong example of how targeted, relevant messaging can outperform broader reach posts in driving meaningful interactions.

3. [The weekend just got better; we’ve got a new AsyncAPI Ambassador, Naresh Jain! 🚀](https://www.linkedin.com/feed/update/urn:li:share:7329113553813114880/)

- Impressions: 1,729
- Engagement: 156
- Likes: 68
- Comments: 6
- Shares: 3
- Clicks: 79
- Engagement Rate: 9.02%

Key Insight: This post maintained a solid 9.02% engagement rate with balanced interaction types, likes, comments, shares, and clicks, showing it resonated well across different audience preferences. The 156 total engagements reflect genuine interest and conversation around the content, making it a strong all-rounder that built both visibility and community dialogue.

## Q3 Outlook

- Host AsyncAPI Munich and AsyncAPI Lagos conferences successfully.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's weird to read it in August, when it already happened


- Post-event engagement: recap content, speaker highlights, and contributor recognition.

- Introduce “Meet the Maintainer” and “First Contributor” series.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't start too many new initiatives without first polishing the existing ones


- Begin prep and campaign for AsyncAPI London (September) and Bengaluru (October).

- Q3 report

We will continue to iterate on our content strategy, building on the insights from this quarter’s performance to strike the right balance between reach and engagement. While broad visibility remains important for brand awareness, our best-performing posts show that targeted, value-driven content, especially around webinars, events, and timely community updates, generates stronger audience interaction. By doubling down on formats and topics that spark conversation and clicks, we can sustain momentum, deepen community connections, and drive even more meaningful engagement in the coming quarter.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading