Let’s break down your two core issues: resolving the 5003 error and correctly fetching data for your custom s.pageName value.

Fixing Error Code 5003 ("Report data may be incomplete") #

This error almost always ties to an invalid report configuration or not handling Omniture’s asynchronous report queue properly. Here’s what to check:

• Include all required report fields: Omniture’s API needs specific parameters depending on the report type. For any valid request, you’ll need:
  • A clear date range (dateFrom, dateTo)
  • At least one metric (e.g., pageviews)
  • At least one dimension (e.g., page for page names)
• Wait for report processing: The Report.Queue* methods return a report ID, but the report isn’t ready to fetch immediately. You must poll Report.Get until the status changes to done (avoid calling it right after queuing).
• Validate credentials and permissions: Double-check your reportSuiteId is correct, and your API user has full reporting access to that suite.

Filtering by s.pageName #

In Omniture, s.pageName maps directly to the Page dimension in your report suite. To target a specific page, use one of these efficient approaches:

Option 1: Filter Directly in the Report Request #

Add an exact search filter to the page dimension to narrow results to your target page name. This reduces the data returned by the API, making it faster to process.

Option 2: Use a Segment (For Complex Filters) #

If you need to combine page name with other conditions (e.g., specific eVar values), create a segment that targets your s.pageName and include it in the report configuration.

Revised Node.js Code Example #

Here’s a complete, working example that addresses both issues:

const Client = require('omniture').Client;
const client = new Client(username, sharedSecret, 'sanJose');

// Configure your report request
const reportConfig = {
  rsid_list: [reportSuiteId],
  reportDescription: {
    reportSuiteID: reportSuiteId,
    dateFrom: '2024-01-01', // Adjust to your date range
    dateTo: '2024-01-31',
    metrics: [{ id: 'pageviews' }], // Add metrics you need (e.g., 'visits')
    elements: [
      { 
        id: 'page', 
        search: { type: 'exact', keywords: ['YourCustomPageName'] } // Filter by exact s.pageName
      },
      { id: 'prop1' }, // Include your custom prop (replace with your prop number)
      { id: 'evar3' }  // Include your custom eVar (replace with your eVar number)
    ],
    type: 'ranked'
  }
};

// Queue the report first
client.request('Report.QueueRanked', reportConfig, (queueErr, queueResponse) => {
  if (queueErr) {
    console.error('Failed to queue report:', queueErr);
    return;
  }

  const reportId = queueResponse.reportID;
  // Poll until the report is ready
  const checkReportStatus = () => {
    client.request('Report.Get', { reportID: reportId }, (getErr, getResponse) => {
      if (getErr) {
        console.error('Failed to fetch report:', getErr);
        return;
      }

      switch(getResponse.status) {
        case 'done':
          // Process your report data here
          console.log('Fetched report data:', getResponse.report);
          // Prop/eVar values will be in the 'elements' section of the response
          break;
        case 'processing':
          // Wait 5 seconds and retry
          setTimeout(checkReportStatus, 5000);
          break;
        default:
          console.error('Report failed with status:', getResponse.status);
      }
    });
  };

  checkReportStatus();
});

Key Notes for Prop/eVar Retrieval #

To pull in s.prop or s.eVar values associated with your page, add them as elements in the reportDescription.elements array (like prop1 or evar3 in the example). The API will return these values alongside the page data, so you can see all tracked parameters for the target page.

Additional Tips #

• If you still get 5003 errors, verify your date range has existing data for the target page (e.g., don’t request a date before the page was launched).
• For trended/overtime reports, adjust the type field to trended or overtime and ensure your metrics/dimensions are compatible with that report type.
• Test your report configuration in Omniture’s UI first (create a similar report in Adobe Analytics) to confirm data exists before using the API.

内容的提问来源于stack exchange，提问作者Dickens A S