The API Product View History page reports in detail the visits and view statistics made to the documentation pages of API products published on the API Portal. This page allows you to analyze which APIs receive more interest, which products users look at more, and the source distribution of portal traffic.
What is API Product View History?
API Product View History is an analysis screen that reports how frequently API products published on the API Portal are viewed by users. This screen is used to measure access statistics of API documentation and user interest in products.Purpose of This Page
Through this page, you can:- Interest Level Analysis: Learn which API products are viewed more
- User Segmentation: Understand whether traffic comes from anonymous visitors or registered users
- Trend Analysis: Track view trends over time
- Documentation Optimization: Determine which products need more documentation
- Promotion Impact Analysis: Measure the impact of announcements or new features on traffic
Interest Level Measurement
Identify which API products are examined more frequently by developers
User Analysis
Analyze the source distribution of portal traffic (Anonymous vs. Registered)
Trend Tracking
Monitor view trends and changes over time
Strategic Decisions
Make data-driven decisions for product portfolio and documentation strategies
Accessing the Page
To access the API Product View History page, follow these steps:1
Login to Manager Interface
Log in to Apinizer Manager interface with administrator privileges
2
Go to Portal Tab
Click on Portal tab in the top menu bar
3
Select API Portal
Click on the relevant portal from the portal list or go to Portal → Settings menu
4
Access View History Page
Click on “API Product View History” or “API Ürün Görüntülenme Geçmişi” option from the left menu or settings page
- Alternatively, you can follow the path: Portal → API Products → View History
API Product View History Screen
Data Analysis and Filtering
This report allows you to analyze the visibility and access details of API products. The filtering options and column descriptions below should be referenced to correctly interpret the data.Time Periods
The time range of reported data is determined through buttons in the top left. Each period is optimized for different analysis needs.Daily
Daily Analysis:
- Lists view counts separately for each day
- Used to monitor real-time traffic changes
- Daily peak hours and intensity analysis can be performed
- Daily interest tracking when a new API product is published
- Daily traffic analysis after announcements or campaigns
- Weekday vs. weekend comparison
Weekly
Weekly Analysis:
- Shows data covering the last 7 days
- Suitable for analyzing weekly usage trends
- Weekday and weekend comparison can be performed
- Tracking weekly view trends
- Determining weekly most popular API products
- Weekly user segmentation analysis
Monthly
Monthly Analysis:
- Presents monthly view totals
- Shows long-term usage and interest changes
- Seasonal trends and growth analysis can be performed
- Calculating monthly growth rates
- Analyzing seasonal changes
- Long-term strategic planning
Time period selection should be made according to the detail level you want to analyze. While daily analysis provides more detailed information, monthly analysis helps you see general trends.
Table Fields and Columns
Detailed descriptions of data fields in the report are as follows:| Column | Description | Usage Purpose | Example |
|---|---|---|---|
| API Product Name | The name of the viewed API product. Shows the full name of the API product published on the portal. | Identifying products with highest access counts. Understanding which APIs are more popular. | Payment API, User Management API |
| Account Name | Identity of the user viewing the page. • Public: Anonymous (not logged in) visitors. • Email: Registered and logged in users. | Distinguishing whether traffic comes from anonymous visitors or existing developers. User segmentation analysis. | Public, [email protected] |
| View Count | Total page view count in the relevant time period. Each page view is counted once. | Numerical magnitude of interest shown to product documentation. Popularity measurement and trend analysis. | 150, 1,234, 5,678 |
API Product Name
Description: This column shows the full name of the API product published on the portal. Each row represents a view record for a specific API product. Features:- API product name is the same as the name defined in Portal → API Products section
- Different user types (Public/Registered) for the same API product are shown in separate rows
- You can go to the relevant API product detail page by clicking on the API product name
- Sort by View Count to identify most popular API products
- Filter to track performance of a specific API product
Account Name
Description: This column shows the identity of the user viewing the API product page. It can take two different values: 1. Public (Open to Everyone):- Represents anonymous visitors who are not logged in
- Users who have not registered on the portal or are not logged in
- These visitors can view API documentation but cannot use the API
- Represents users who have registered and logged into the portal
- Example:
[email protected],[email protected] - These users can use the API and register applications
Traffic Source Analysis
Traffic Source Analysis
Public vs. Registered User Comparison:
- If Public traffic is high: Portal promotion is working well, but registration rate may be low
- If registered user traffic is high: Existing developers are actively examining APIs
- If Public traffic is high, optimize the registration process
- If registered user traffic is high, analyze API usage rates
User Segmentation
User Segmentation
Interest Areas of Different User Groups:
- Which API products do anonymous visitors look at more?
- Which API products do registered users look at more?
- Make better promotion for APIs that anonymous visitors are interested in
- Prepare more detailed documentation for APIs that registered users are interested in
View Count
Description: This column shows how many times the relevant API product page was viewed within the selected time period. Each page view is counted once. Features:- Shown as a numerical value (e.g.,
150,1,234,5,678) - Multiple views by the same user are counted separately
- Shows total view count according to time period
- Sort by View Count to identify most popular API products
- Compare different time periods for trend analysis
- Calculate growth rates
View Count shows the number of page views. This is not the actual usage count (API calls) of the API. Use the Analytics module for actual API traffic.
Usage Scenarios and Analysis Examples
You can perform various analyses and make strategic decisions using the API Product View History page. Below, the most common usage scenarios are explained in detail.Scenario 1: Interest Level Analysis and Popularity Determination
To determine which API products receive more interest and manage the product portfolio accordingly:1
Select Time Period
Select the time period you want to analyze:
- Daily: Last 24 hours or a specific day
- Weekly: Last 7 days
- Monthly: Last 30 days or a specific month
2
Sort by View Count
Sort the table by View Count column (high to low):
- API products with highest view counts appear at the top
- This shows the most popular API products
3
Popularity Analysis
Analyze the results:Most Popular APIs:
- Which API products are viewed most?
- Is the documentation for these APIs sufficient?
- Are additional resources needed for these APIs?
- Which API products are viewed less?
- Is the promotion for these APIs sufficient?
- Is documentation improvement needed?
4
Strategic Decisions
Take action based on analysis results:For Popular APIs:
- Prepare more detailed documentation
- Add example code and tutorials
- Increase support resources
- Conduct promotion and marketing activities
- Review and improve documentation
- Add usage examples and case studies
Scenario 2: User Segmentation and Traffic Analysis
To analyze the source distribution of portal traffic and perform user segmentation:1
Filter by Account Name
Filter or group the table by Account Name column:Public (Anonymous) Traffic:
- Examine records where Account Name = “Public”
- Calculate total Public view count
- Examine records where Account Name = Email address
- Calculate total registered user view count
2
Calculate Traffic Ratio
Calculate the ratio of both traffic types:Example Calculation:
- Total views: 10,000
- Public views: 7,000 (70%)
- Registered user views: 3,000 (30%)
- If Public traffic is high: Portal promotion is good, but registration rate may be low
- If registered user traffic is high: Existing developers are active
3
Segment-Based Analysis
Perform separate analysis for each segment:Public Traffic Analysis:
- Which APIs are viewed more by anonymous visitors?
- Are promotion materials sufficient for these APIs?
- Is it necessary to optimize the registration process?
- Which APIs are viewed more by existing developers?
- Is documentation sufficient for these APIs?
- Are API usage rates consistent with view rates?
4
Optimization Strategy
Optimize based on segment analysis:For Public Traffic:
- Optimize portal home page
- Improve API promotion pages
- Simplify registration process
- Organize registration incentive campaigns
- Improve documentation quality
- Add example code and tutorials
- Prepare API usage guides
- Expand support resources
Scenario 3: Documentation Optimization
To review documentation content of products with high view counts but low usage rates:1
Identify High Views, Low Usage
Identify products with high View Count but low API usage:Criteria:
- View Count: High (e.g., 1,000+)
- API Usage: Low (check from Analytics)
- Application Registrations: Few
- Users are viewing the API but not using it
- Documentation may be insufficient or confusing
- Example code or usage guide may be missing
2
Documentation Review
Review the documentation of the relevant API product:Things to Check:
- Is documentation clear and understandable?
- Are there example codes and usage scenarios?
- Are API endpoints explained in detail?
- Is there error handling and troubleshooting information?
- Is there a Quick Start guide?
3
Improvement Plan
Plan documentation improvements:Can Be Added:
- More detailed API descriptions
- Step-by-step usage guides
- Example code and snippets
- Common use cases
- Troubleshooting section
- FAQ (Frequently Asked Questions)
4
Post-Improvement Tracking
Track results after improvements:
- Did view count change?
- Did API usage rate increase?
- Did application registrations increase?
- How are user feedbacks?
Scenario 4: Promotion Impact Analysis
To measure the impact of announcements or newly published features on portal traffic:1
Before and After Comparison
Compare data before and after announcement or new feature:Before Period:
- View counts for 7 days before announcement
- Daily average views
- View counts for 7 days after announcement
- Daily average views
- Growth rate = ((After - Before) / Before) × 100
2
Impact Analysis
Analyze the impact of the announcement:High Impact Indicators:
- Significant increase in view count
- Increase in relevant API products
- Increase in new user registrations
- No change in view count
- No increase in user interest
3
Campaign Optimization
Optimize campaign based on analysis results:If High Impact:
- Organize similar campaigns
- Use successful channels more
- Expand content
- Change campaign channels
- Review message
- Re-evaluate target audience
Usage Areas and Strategic Decisions
Data obtained from this report can be used as input in the following management decisions:Interest Level Analysis
Identifying which API products are examined more frequently by developers and managing the product portfolio accordingly. Allocate more resources for popular APIs, promote less popular APIs.
User Segmentation
Analyzing the source distribution of portal traffic (Anonymous vs. Registered User). Develop and optimize different strategies for each segment.
Documentation Optimization
Reviewing documentation content of products with high view counts but low usage rates. Increase usage rates by improving documentation quality.
Promotion Impact Analysis
Measuring the impact of announcements or newly published features on portal traffic. Evaluate and optimize campaign success.
Product Portfolio Management
Deciding which API products to invest more in. Support popular APIs, review less used APIs.
Resource Planning
Planning the distribution of documentation, support, and development resources. Allocate more resources for APIs that receive most interest.
Technical Notes and Important Warnings
Data Update:View data is updated in real-time. However, there may be a short delay for calculating totals (usually a few minutes).
Conclusion
The API Product View History page is a powerful tool for portal administrators to analyze API product popularity, user interest, and traffic trends. By using this page regularly, you can: ✅ Identify which APIs are more popular✅ Perform user segmentation and analyze traffic sources
✅ Make data-driven decisions for documentation optimization
✅ Measure the impact of promotion campaigns
✅ Develop product portfolio and resource planning strategies
Data-Driven Decisions
Make strategic decisions and optimize product portfolio using view data
User Needs
Understand which APIs users are interested in and allocate resources according to their needs
Continuous Improvement
Continuously improve portal performance through regular analysis
Competitive Advantage
Gain competitive advantage by supporting popular APIs